Details
-
Bug
-
Resolution: Fixed
-
Medium
-
6.9.1, 6.9.2
-
3
-
Severity 2 - Major
-
Description
Issue Summary
When an LDAP group is the same as a group in Bamboo internal directory, incremental synchronization will be broken.
The bug CWD-5308 affects Bamboo Embedded crowd 3.2.6
2019-07-23 17:21:03,703 INFO [atlassian-scheduler-quartz2.local_Worker-4] [DbCachingRemoteChangeOperations] scanned and compared [ 0 ] groups for update in DB cache in [ 3ms ]2019-07-23 17:21:03,703 INFO [atlassian-scheduler-quartz2.local_Worker-4] [DbCachingRemoteChangeOperations] scanned and compared [ 0 ] groups for update in DB cache in [ 3ms ]2019-07-23 17:21:03,703 INFO [atlassian-scheduler-quartz2.local_Worker-4] [DirectoryCacheImplUsingChangeOperations] synchronized [ 0 ] groups in [ 3ms ]2019-07-23 17:21:03,703 WARN [atlassian-scheduler-quartz2.local_Worker-4] [UsnChangedCacheRefresher] Failed to fetch user by objectGUID '9206945c5aee8e498f847c9129b76eae' from ActiveDirectory2019-07-23 17:21:03,703 ERROR [atlassian-scheduler-quartz2.local_Worker-4] [DbCachingRemoteDirectory] Incremental synchronisation for directory [ 2949121 ] was unexpectedly interrupted, falling back to a full synchronisationcom.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresherIncSyncException: Problems while looking up users by objectGUID in ActiveDirectory detected, falling back to a full sync. at com.atlassian.crowd.directory.synchronisation.cache.UsnChangedCacheRefresher.lambda$synchroniseGroupChanges$4(UsnChangedCacheRefresher.java:451) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
Workaround
Use distinct unique group names for Bamboo internal group and the LDAP directory.