Details
-
Bug
-
Resolution: Fixed
-
Low
-
2.2.1
-
None
-
None
Description
The RemoteDirectorySynchronisedEvent is fired too early. Currently it is fired in com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher#synchroniseAll (or com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher#synchroniseChanges), before the directory attribute IS_SYNCHRONISING is reset (in com.atlassian.crowd.manager.directory.DirectorySynchroniserHelperImpl#updateSyncEndTime), making it impossible to reliably wait until the synchronisation job completes. It needs to be fired after this attribute is updated instead.