-
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
-
[CWD-2704] LDAP group membership works only if the DN matches CASE-SENSITIVE
Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1509526 ] | New: JAC Bug Workflow v3 [ 3365568 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Link |
New:
This issue is related to |
Link | New: This issue is related to CONFCLOUD-24515 [ CONFCLOUD-24515 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391613 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1509526 ] |
Workflow | Original: Crowd Development Workflow v2 [ 352121 ] | New: Simplified Crowd Development Workflow v2 [ 1391613 ] |
Fix Version/s | New: 2.4.2 [ 25495 ] | |
Fix Version/s | Original: 2.4.1 [ 22991 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Verified [ 10005 ] | New: Resolved [ 5 ] |
Status | Original: Needs Verification [ 10004 ] | New: Verified [ 10005 ] |
Status | Original: Open [ 1 ] | New: Needs Verification [ 10004 ] |