[jira] [Resolved] (DIRSERVER-1922) Not Operator in Ldap Filter on Indexed Attributes

["Kiran Ayyagari (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRSERVER-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Ayyagari resolved DIRSERVER-1922.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-M16
         Assignee: Kiran Ayyagari

This is a bug, fixed it here http://svn.apache.org/r1546397 

Thank you very much for reporting.

> Not Operator in Ldap Filter on Indexed Attributes
> -------------------------------------------------
>
>                 Key: DIRSERVER-1922
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1922
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M15
>         Environment: Debian Linux OpenJDK 7
>            Reporter: Michael Simon
>            Assignee: Kiran Ayyagari
>             Fix For: 2.0.0-M16
>
>
> Launch ApacheDS freshly downloaded from Website. Create a user in dc=example,dc=com
> dn: uid=test,dc=example,dc=com
> objectClass: inetOrgPerson
> objectClass: organizationalPerson
> objectClass: person
> objectClass: top
> cn: test
> sn: test
> uid: test
> Perform a search with filter (!(uid=quak)). 
> Perform a search with filter (!(sn=quak)).
> First search yields no result. Second yields 2 results. Uid is indexed, sn is not.
> This behavior is a bit annoying, because some Linux NSLCD implementation use the LDAP Filter (&(objectClass=posixAccount)(!(|(uidNumber=0)(gidNumber=0)))). If you have an index on either uidNumber or gidNumber it won't work anymore, if you don't have the root user in your directory.



--
This message was sent by Atlassian JIRA
(v6.1#6144)