Search filters with wrong case in attribute names lead to wrong result

• Key: DIRSERVER-389
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Alex Karasulu
• Reporter: Stefan Zoerner

Description

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.