-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
2.4.4, 2.5
-
2
-
Severity 3 - Minor
-
The incremental sync with AD does not play well with duplicate groups. For example:
- Set up an AD with multiple groups with the same CN.
- Do a full sync. Note the group is ignored because the sync detects multiple groups (as was implemented in
CWD-2504). - Add a user to one of the groups and do and sync again.
- (BUG) The group you changed will now appear in Crowd.
The problem is that the incremental sync will only see the group that changed and incorrectly assume that there is now only one group.
- Restart crowd and sync again. This will be a full sync.
- The group will have again disappeared from Crowd because the full sync again detects the duplicate groups.
So basically when Crowd does a full sync it will make a duplicate group disappear. However, the duplicate group may appear if one of the two groups is changed before an incremental sync.
- is related to
-
CWD-2504 Synchronization with JIRA/Confluence fail with duplicate entry
-
- Closed
-
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Crowd Data Center, please check our public roadmap.
Kind regards,
Crowd Data Center