[
https://issues.apache.org/jira/browse/DIRSERVER-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-1152.
----------------------------------------
Resolution: Duplicate
Seems to have been fixed in trunk :
https://issues.apache.org/jira/browse/DIRSERVER-1061
> OR search with multiple attributes if one is bad, search fails
> --------------------------------------------------------------
>
> Key: DIRSERVER-1152
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1152
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: Running on windows under JBoss
> Reporter: Steve hammond
> Priority: Minor
>
> Doing a search from LDAP Studio, or from an Open LDAP Client. I have a
> search string with multiple attributes trying to find a name. The client is
> required to include some attributes that do not even exist on my server.
> Depending on the format of the search string, one succeeds and one fails,
> even tho they are searching the same data with the same attributes. I would
> like both to succeed and return values for attributes that do match.
> ldap://10.33.32.228:389/ou=users,ou=ReadiManager??sub?(|(|(|(|(ldapDisplayName=a*))(|(name=a*))(|(middleName=a*))(cn=a*)(sn=a*))(givenName=a*))(displayName=a*))
> works fine, returns one result in my system, nothing is ine logs.
> (|(ldapDisplayName=a*)(name=a*)(middleName=a*)(cn=a*)(sn=a*)(givenName=a*)(displayName=a*))
> does not return an error, but also does not return any rows. The following
> appears in the log:
> 13:07:17,754 WARN [NormalizingVisitor] (pool-2-thread-5) Removing leaf node
> based on undefined attribute 'ldapdisplayname' from filter.
> 13:07:17,754 WARN [NormalizationService] (pool-2-thread-5) Undefined
> branchnode filter without child nodes not evaluted at all. Returning empty
> enumeration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
