-
Suggestion
-
Resolution: Timed out
-
None
-
None
-
None
Currently we use cn attribute for group names, but this value is not always unique, which is a requirement for successful synchronisation. We already use sAMAccountName for user names. We also need to add a Group Name RDN attribute, and change SpringLDAPConnector#addGroup to use it when generating dn.
- causes
-
JRASERVER-26164 JIRA uses the CN attribute for Active Directory LDAP, but this is not guaranteed unique.
-
- Gathering Impact
-
- relates to
-
CWD-2431 AD Groups with same CN but unique sAMAccountName causes Crowd to sync for a long time/indefinitely
-
- Closed
-
-
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
[CWD-2441] Use sAMAccountName attribute for group name by default when using Active Directory
Workflow | Original: JAC Suggestion Workflow [ 3388266 ] | New: JAC Suggestion Workflow 3 [ 3630140 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1390057 ] | New: JAC Suggestion Workflow [ 3388266 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Resolution | New: Timed out [ 10 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Link | New: This issue causes JRACLOUD-26164 [ JRACLOUD-26164 ] |
Link | New: This issue relates to CONFCLOUD-23213 [ CONFCLOUD-23213 ] |
Workflow | Original: Crowd Development Workflow v2 [ 292403 ] | New: Simplified Crowd Development Workflow v2 [ 1390057 ] |
Link | New: This issue relates to CONF-23213 [ CONF-23213 ] |
Regular Expression | New: 'jira.cwd_membership' with unique index 'uk_mem_parent_child_type'. |
Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Crowd features that solve problems for the greater customer base. To that end, we aim to keep our issues up-to-date so that they accurately reflect current customer needs. Because there has been no customer activity on this issue in a long time, we have marked it as closed. If you still feel that this issue is still relevant to your needs, please feel free to raise a new issue and link to this one.
If you would like to see how we select features for a new release, please read http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy.