-
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