-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
None
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Problem
If there exist a directory in LDAP with same tree structure differing only in case, then there will be partial importation of entries during synchronization. Here is a scenario to depict:
- For example a tree with the following structure results in a situation where user1,user2 and user3 will be synchronized succesfully which is perfect:
cn=user1,ou=people,o=sevenSeas,dc=example,dc=com cn=user2,ou=people,o=sevenSeas,dc=example,dc=com cn=user3,ou=people,o=sevenSeas,dc=example,dc=com
- If the subtree differes a little bit and the base DN is defined as ou=people,o=sevenSeas,dc=example,dc=com, then only user1 and user2 will be synchronized
cn=user1,ou=people,o=sevenSeas,dc=example,dc=com cn=user2,ou=people,o=sevenSeas,dc=example,dc=com cn=user3,ou=PEOPLE,o=sevenSeas,dc=example,dc=com
Workaround
The workaround at the moment is to enable naive DN matching. This should be fine with memberDNs in compact format. membership can still be broken if memberDNs are not in compact view.
- relates to
-
CWD-2704 LDAP group membership works only if the DN matches CASE-SENSITIVE
- Closed
-
JRACLOUD-26831 CASE-SENSITIVE DN causes partial synchronization of LDAP membership.
- Closed