directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Commented: (DIREVE-294) Search filters with wrong case in attribute names lead to wrong result
Date Wed, 26 Oct 2005 03:38:55 GMT
    [ ] 

Alex Karasulu commented on DIREVE-294:

I am really sorry about this screw up.  It was a bug deep in the BootstrapOidRegistry that
caused this.  For some reason I think this was the first time we triggered the execution of
the code this way. Anyhow its fix and I appologize for any runaround this may have caused

> Search filters with wrong case in attribute names lead to wrong result
> ----------------------------------------------------------------------
>          Key: DIREVE-294
>          URL:
>      Project: Directory Server
>         Type: Bug
>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu
>      Fix For: 0.9.3

> Search filters which use attribute names with "wrong" case cause the search operation
to return nothing. Example:
> $ ldapsearch -D "uid=admin,ou=system" -w ***** -p 10389 -b "dc=apache,dc=org" -s base
> (nothing)
> $
> But the following still works as expected:
> $ ldapsearch -D "uid=admin,ou=system" -w secret -p 10389 -b "dc=apache,dc=org" -s base
> dc=apache,dc=org
> dc=apache
> objectClass=extensibleObject
> objectClass=domain
> objectClass=top
> I assume the error is due to changes in class NormalizationService (package org.apache.ldap.server.normalization)
done to fix DIREVE-274, because if "wrong" attributes are used, this interceptor raises WARN
messages like 
> [23:37:27] WARN [org.apache.ldap.server.normalization.NormalizationService] - undefined
filter based on undefined attributeType 'Objectclass' not evaluated at all.  Returning empty
> which explains the behavior above. 
> Btw.: The behavior causes Softerra LDAP Administrator 3.2.1 to fail during the exploration
of entries. This is how I found it.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message