[
https://issues.apache.org/jira/browse/DIRSERVER-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436409#comment-13436409
]
Emmanuel Lecharny commented on DIRSERVER-1744:
----------------------------------------------
And for your information, the third filter returns nothing on trunk (haven't
tested it on 2.0.0-M7) so it seems that the pb has been fixed since M6...
> Compex LDAP search filters returning unmatched objects
> ------------------------------------------------------
>
> Key: DIRSERVER-1744
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1744
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 2.0.0-M6
> Environment: CentOS 5.6
> Reporter: Richard Hardy
>
> I used ApacheDirectoryStudio-linux-x86_64-2.0.0.v20120224 and created an
> Apache DS server with it. The root DSE reported version of this server is
> 2.0.0-M6.
> The same problem is also present in the Apache DS bundled with
> ApacheDirectoryStudio-linux-x86_64-1.5.3.v20100330
> I created the dc=example,dc=com context and the following group
> dn: cn=g1,dc=example,dc=com
> objectClass: groupOfNames
> objectClass: top
> member: dc=example,dc=com
> cn: g1
> I Searched with
> ldapsearch -x -h localhost -p 10389 -D uid=admin,ou=system -w secret -b
> dc=example,dc=com '(&(objectclass=groupofnames)(owner=*))'
> nothing is returned which is correct
> ldapsearch -x -h localhost -p 10389 -D uid=admin,ou=system -w secret -b
> dc=example,dc=com '(&(|(objectclass=groupofnames))(owner=*))'
> nothing is returned as expected
> ldapsearch -x -h localhost -p 10389 -D uid=admin,ou=system -w secret -b
> dc=example,dc=com '(&(|(&(objectclass=groupofnames)))(owner=*))'
> the group g1 is returned which is not expected, and other directories do not
> return objects with this same setup. The actual filters I want to use are
> more complicated than this, but this is the simplest one that demonstrates
> the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira