[ http://issues.apache.org/jira/browse/DIREVE-294?page=all ]
Alex Karasulu resolved DIREVE-294:
----------------------------------
Resolution: Fixed
Committed fix in revision 328545 here:
http://svn.apache.org/viewcvs.cgi?rev=328545&view=rev
> Search filters with wrong case in attribute names lead to wrong result
> ----------------------------------------------------------------------
>
> Key: DIREVE-294
> URL: http://issues.apache.org/jira/browse/DIREVE-294
> 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 "(Objectclass=*)"
> (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 "(objectClass=*)"
> 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 enumeration.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
