-
Suggestion
-
Resolution: Fixed
-
Crowd Standalone
1.6.0_27 (32-bit)
Windows Server 2008 R26.1
If Crowd is connected to an Active Directory cluster it does not properly support incremental synchronization since the usnChanged attribute value is not replicated between AD servers:
2017-08-25 00:28:51,783 ERROR [Caesium-1-3] [atlassian.crowd.directory.DbCachingDirectoryPoller] pollChanges Error occurred while refreshing the cache for directory [ 21757953 ]. com.atlassian.crowd.exception.OperationFailedException: Error looking up attributes for highestCommittedUSN
See
Crowd should be enhanced to know which server it is connected to and:
- Perform an incremental synchronization if it connects to the same server a second time concurrently
- Perform a full synchronization if it connects to a different server
See Users are Unable to Log In Due to 'Error looking up attributes for highestCommittedUSN'
- blocks
-
CONFSERVER-23073 Support load-balanced LDAP/AD servers with Confluence
- Closed
- depended on by
-
BSERV-11111 Support load-balanced LDAP/AD servers with Bitbucket Server
- Closed
- is related to
-
CWD-3320 Incremental synch in MS Active Directory does not always work after intial synch
- Closed
-
JRASERVER-24133 Support load-balanced LDAP/AD servers with JIRA
- Closed
- is cloned by
-
KYAK-237 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...