You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Nick Faiz (JIRA)" <di...@incubator.apache.org> on 2005/09/13 03:54:30 UTC
[jira] Created: (DIREVE-251) case sensitivity in matching objectClass in search filter
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.3
Reporter: Nick Faiz
Assigned to: Alex Karasulu
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
[jira] Closed: (DIRSERVER-347) case sensitivity in matching
objectClass in search filter
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-347.
---------------------------------------
Closing all issues created in 2005 and before which are marked resolved
> case sensitivity in matching objectClass in search filter
> ---------------------------------------------------------
>
> Key: DIRSERVER-347
> URL: https://issues.apache.org/jira/browse/DIRSERVER-347
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Nick Faiz
> Assigned To: Alex Karasulu
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIREVE-251) case sensitivity in matching objectClass in search filter
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-251?page=all ]
Alex Karasulu updated DIREVE-251:
---------------------------------
Version: 0.9.2
(was: 0.9.3)
> 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
>
> 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
[jira] Commented: (DIREVE-251) case sensitivity in matching objectClass in search filter
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-251?page=comments#action_12324411 ]
Alex Karasulu commented on DIREVE-251:
--------------------------------------
To confirm this fix actually worked you must delete your old database. Without deleting the database this bug will reappear because the wrong index values for objectClass are stored.
> 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
Re: [jira] Commented: (DIREVE-251) case sensitivity in matching objectClass in search filter
Posted by Chris Betts <ch...@pegacat.com>.
Hi Alex,
if you want to be brutally accurate, shouldn't you be matching by
the object class OID, rather than the string name?
JX *doesn't* do this (yet) and it creates all sorts of trouble
because people can have multiple names for the same object class...
but of course converting makes the code that much more complex. If
you can architect it in early though, it might save you trouble down
the track?
cheers,
- Chris
On 13/09/2005, at 12:54 PM, Alex Karasulu (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DIREVE-251?
> page=comments#action_12323308 ]
>
> Alex Karasulu commented on DIREVE-251:
> --------------------------------------
>
> I was sure filter value normalization was taken into account before
> but several things have been changing lately. However looking at
> the code we must make sure values in filter attribute value
> assertions must be normalized. Also any Assertions must normalize
> values in entries they compare filter values to. I thought this
> was done long ago but I'll recheck all the pathways.
>
> The bug is very real though .. just confirmed it.
>
>
>> 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
>>
>
>
>>
>> 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
>
>
[jira] Commented: (DIREVE-251) case sensitivity in matching objectClass in search filter
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-251?page=comments#action_12323308 ]
Alex Karasulu commented on DIREVE-251:
--------------------------------------
I was sure filter value normalization was taken into account before but several things have been changing lately. However looking at the code we must make sure values in filter attribute value assertions must be normalized. Also any Assertions must normalize values in entries they compare filter values to. I thought this was done long ago but I'll recheck all the pathways.
The bug is very real though .. just confirmed it.
> 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
>
> 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
[jira] Resolved: (DIREVE-251) case sensitivity in matching objectClass in search filter
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ 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