-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
2.6, 2.5.3, 2.4.8
-
None
Currently, this scenario will fail because crowd will attempt to add a row with a duplicate primary key to the membership database table.
- 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
-
- relates to
-
CWD-3147 If a user exists in two directories in an application, and is added to a group in one directory that it was already in the other, clients get duplicate key errors
-
- Closed
-
[CWD-3182] Should not fail to add a user membership to a group for a Directory if the membership already exists
Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1510748 ] | New: JAC Bug Workflow v3 [ 3365683 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Link | New: This issue causes JRACLOUD-31793 [ JRACLOUD-31793 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391287 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1510748 ] |
Workflow | Original: Crowd Development Workflow v2 [ 498548 ] | New: Simplified Crowd Development Workflow v2 [ 1391287 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Technical Review [ 10028 ] | New: Resolved [ 5 ] |
Summary | Original: Should not fail to add a user mebership to a group for a Directory if the membership already exists | New: Should not fail to add a user membership to a group for a Directory if the membership already exists |
Status | Original: In Progress [ 3 ] | New: Technical Review [ 10028 ] |
Issue resolved by
CWD-3198making failure detectable andCWD-3188falling back to full synchronisation.