-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
None
Problem
LDAP group membership works only if the DN matches CASE-SENSITIVE. See LDIFs attached.
After setting LDAP integration and synchronize, the result is shown as follow:
- In groupB, it has all the three users listed as members.
- In groupA, it has only two users listed as members. The user3 is missing
Fix
There is none yet.
Workaround
There is none yet.
- is incorporated by
-
CWD-2760 No way to configure DN subtree matching to be case-insensitive and handle whitespace properly
-
- Closed
-
- is related to
-
CONFSERVER-24515 CASE-SENSITIVE DN causes partial synchronization of LDAP membership.
-
- Closed
-
-
JRACLOUD-26831 CASE-SENSITIVE DN causes partial synchronization of LDAP membership.
-
- Closed
-
-
JRASERVER-26831 CASE-SENSITIVE DN causes partial synchronization of LDAP membership.
-
- Closed
-
Some users are facing problem with JIRA and crowd direct connection to LDAP without following through crowd intermediary. Will the fix for this issues be incorporated in the embedded crowd in other applications?.