-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
If the stream of events received during incremental synchronisation with a remote Crowd directory is inconsistent, Crowd may attempt to re-add members to groups they're already in. If this fails, Crowd should fall back to full synchronisation for that directory.
- causes
-
JRASERVER-31793 JIRA attempts to apply group memberships when synchronising from a remote directory even if they already exist, causing a duplicate key violation
-
- Closed
-
- Discovered while testing
-
CWD-3182 Should not fail to add a user membership to a group for a Directory if the membership already exists
-
- Closed
-
- incorporates
-
CWD-3917 Application syncs from Crowd fail due to "com.atlassian.crowd.model.event.AliasEvent" incorrectly invoked
-
- Closed
-
- is related to
-
CWD-2714 Crowd needs to detect when an incremental Update is not possible and react
-
- Long Term Backlog
-
- was split into
-
CWD-3198 DAOs should throw checked exceptions as declared in interfaces
- Closed
[CWD-3188] Failing incremental Crowd/Crowd synchronisation should fall back to full synchronisation
Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1508764 ] | New: JAC Bug Workflow v3 [ 3365677 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Link | New: This issue causes JRACLOUD-31793 [ JRACLOUD-31793 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1389922 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1508764 ] |
Workflow | Original: Crowd Development Workflow v2 [ 513770 ] | New: Simplified Crowd Development Workflow v2 [ 1389922 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 63096 ] |
Hi rmota@vsc-technologies.com,
Crowd 2.5.0 does not contain the fix for this issue. It was added in the 2.5.4 release of Crowd 2.5.x. I suggest you upgrade to the most recent release of the Crowd 2.5.x series, or even better, to the most recent release of Crowd to receive this and many other fixes.