Can someone tell me what the expected behavior is for the following setup?
Setup: One MLS server connecting 50+ Spectro servers, each having their own landscape.
Our admins and managers log into the MLS directly to get the overview of the network. Each site has local users who log into their local instance. When we add/delete accounts, we do it through the MLS, and eventually it will sync its way down to the landscape where it is needed.
We see problems when a landscape is unavailable (network availability). If a user was deleted while their landscape was offline, it either complains, or removes it, but only until the landscape comes back up and the user is re-added to the MLS.
We are trying to streamline our user password management, and the above is just making a mess of everything. The MLS should be the authority for users and all connected landscapes should sync their user database to the MLS. It would be even better if only user accounts used in the landscape were synced (maybe that is how it works, I don't know).
Is there a way to force a sync of the user models across all landscapes?