-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
None
Currently, if there is a duplicate group name in an LDAP directory, the duplicate group is dropped to allow synchronisation to continue. This was implemented in CWD-2504.
It would be ideal if the memberships of these two groups could be combined. Users will not necessarily be aware that the duplicate group was dropped but may realize they are missing memberships for expected groups. The following is logged in atlassian-confluence.log:
WARN [scheduler_Worker-1] [directory.ldap.cache.AbstractCacheRefresher] filterOutDuplicateGroups group[<groupname>] duplicated in remote directory. Ignoring group.
Please see the discussion in the linked CONF-23213
- blocks
-
CONFCLOUD-23213 Merge memberships for groups with duplicate names during LDAP directory sync
- Gathering Interest
-
CONFSERVER-23213 Merge memberships for groups with duplicate names during LDAP directory sync
- Gathering Interest
- is duplicated by
-
CWD-4345 Crowd should aggregate multiple groups of the same name in an LDAP directory
- Closed
- is related to
-
CWD-2504 Synchronization with JIRA/Confluence fail with duplicate entry
-
- Closed
-
[CWD-3227] Merge memberships for groups with duplicate names during LDAP directory sync
Workflow | Original: JAC Suggestion Workflow [ 3388882 ] | New: JAC Suggestion Workflow 3 [ 3630897 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1393413 ] | New: JAC Suggestion Workflow [ 3388882 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Link | New: This issue blocks CONFCLOUD-23213 [ CONFCLOUD-23213 ] |
Workflow | Original: Crowd Development Workflow v2 [ 515870 ] | New: Simplified Crowd Development Workflow v2 [ 1393413 ] |
Regular Expression | New: duplicated in remote directory\. Ignoring group\. |
Description |
Original:
Currently, if there is a duplicate groupname in an LDAP directory, the duplicate group is dropped to allow synchronisation to continue. This was implemented in It would be ideal if the memberships of these two groups could be combined. Please see the discussion in the linked CONF-23213 |
New:
Currently, if there is a duplicate group name in an LDAP directory, the duplicate group is dropped to allow synchronisation to continue. This was implemented in It would be ideal if the memberships of these two groups could be combined. Users will not necessarily be aware that the duplicate group was dropped but may realize they are missing memberships for expected groups. The following is logged in atlassian-confluence.log: {code} WARN [scheduler_Worker-1] [directory.ldap.cache.AbstractCacheRefresher] filterOutDuplicateGroups group[<groupname>] duplicated in remote directory. Ignoring group. {code} Please see the discussion in the linked CONF-23213 |
Link | New: This issue blocks CONF-23213 [ CONF-23213 ] |