AT:

• on startup and in a configured interval users & groups authorized to access Optimize are populated into the Searchable Identity cache
• the sync can be disabled via configuration
• if one sync exceeds the interval no new sync is started, at any time there is at max one sync running at a time
• every sync run creates a new instance of the searchable cache, once complete it replaces the previous cache (this way we get rid of deleted users/group automatically and search operations are only executed on one consistent synced dataset)
• the sync iterates all connected engines and collects present users, a particular unique userId or groupId is only imported once, first one wins