directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Betts <ch...@pegacat.com>
Subject Re: [jira] Commented: (DIREVE-251) case sensitivity in matching objectClass in search filter
Date Tue, 13 Sep 2005 03:08:09 GMT
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
>
>


Mime
View raw message