Description
Was originally raised against JIRA as JRA-26458
Incremental synch is based on the highestCommittedUSN attribute, and this is not cluster-safe AFAIK, so I imagine that this is one way it coud be broken, however at least one customer claims it happens for them even when attaching to a single node.
To make matters worse, incremental synch is on by default and is hidden in the advanced configuration.
Attachments
Issue Links
- causes
-
JRASERVER-26458 Synchronization of users that are added to a particular AD group that is configured to automatically become JIRA users doesn't work after the initial synch
-
- Closed
-
- is related to
-
CWD-3715 Prevent crowd cache corruption due to rapid changes in Active Directory
- Closed
- relates to
-
- Closed