You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2005/09/13 06:50:57 UTC
[jira] Resolved: (DIREVE-251) case sensitivity in matching objectClass in search filter
[ http://issues.apache.org/jira/browse/DIREVE-251?page=all ]
Alex Karasulu resolved DIREVE-251:
----------------------------------
Fix Version: 0.9.3
Resolution: Fixed
Commited changes for a fix in revision 280496 here:
http://svn.apache.org/viewcvs.cgi?view=rev&rev=280496
Note main problem was the fact that a proper normalizer comparator pair was not being used for the objectIdentifierMatch matchingRule which objectClass depends on. Besides this we made several improvments to the handling code.
> case sensitivity in matching objectClass in search filter
> ---------------------------------------------------------
>
> Key: DIREVE-251
> URL: http://issues.apache.org/jira/browse/DIREVE-251
> Project: Directory Server
> Type: Bug
> Components: protocol
> Versions: 0.9.2
> Reporter: Nick Faiz
> Assignee: Alex Karasulu
> Fix For: 0.9.3
>
> ObjectClass matching in search filters is case sensitive. Is this deliberate (need to check in rfc 2254)?
> OpenLDAP, on the other hand, does a case insensitive match.
> A case sensitive match is not particularly helpful in this circumstance.
> [nickf@little-creatures ~]$ ldapsearch -D 'uid=admin,ou=system' -h localhost -p 10389 -x -w secret -b 'ou=users,ou=system' '(&(&(cn=*)(member=cn=groupA,ou=groups,ou=system))(objectClass=inetorgperson))'
> ...
> # search result
> search: 2
> result: 0 Success
> matchedDN: ou=users,ou=system
> [nickf@little-creatures ~]$ ldapsearch -D 'uid=admin,ou=system' -h localhost -p 10389 -x -w secret -b 'ou=users,ou=system' '(&(&(cn=*)(member=cn=groupA,ou=groups,ou=system))(objectClass=inetOrgPerson))'
> ...
> # search result
> search: 2
> result: 0 Success
> matchedDN: ou=users,ou=system
> # numResponses: 9
> # numEntries: 8
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira