-
Bug
-
Resolution: Handled by Support
-
Medium
-
None
-
1.5.2
-
None
LDAP queries in general should not be "contains" or "starts with" or "like". I'm getting whacked by my administrator because the crowd queries are needlessly complex and are all "contains" - i.e. ray_harrison. The system should really default to equals (i.e. exact match) and provide the ability to customize how they are done. Also, there is no need at all to force an object class search. As an example - in Active Directory, all you should have to do is search for sAMAccountName=
{input user}with nothing else needed. Unfortunately, I will have to default to the internal LDAP mechanisms in your other products until this can be worked through - great concept though!
[CWD-1318] LDAP Directory Queries "Contains" Causes Issues
Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1510056 ] | New: JAC Bug Workflow v3 [ 3364924 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392780 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1510056 ] |
Workflow | Original: Crowd Development Workflow v2 [ 272057 ] | New: Simplified Crowd Development Workflow v2 [ 1392780 ] |
Workflow | Original: JIRA Bug Workflow v2 [ 173409 ] | New: Crowd Development Workflow v2 [ 272057 ] |
Workflow | Original: jira [ 147956 ] | New: JIRA Bug Workflow v2 [ 173409 ] |
Resolution | New: Handled by Support [ 8 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |