directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirill Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRSERVER-766) uniqueMember attribute compare does not seem to work properly (uniqueMemberMatch is not implemented?)
Date Tue, 07 Nov 2006 08:38:52 GMT
     [ http://issues.apache.org/jira/browse/DIRSERVER-766?page=all ]

Kirill Kovalenko updated DIRSERVER-766:
---------------------------------------

    Attachment: example.ldif

This is a slightly modified standard example file  that comes with Netscape DS. It can be
imported to Apache DS to reproduce the issue. 

> uniqueMember attribute compare does not seem to work properly (uniqueMemberMatch is not
implemented?)
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-766
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-766
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: Windows XP SP2, Java 1.5.06
>            Reporter: Kirill Kovalenko
>         Attachments: example.ldif
>
>
> When it comes to search attributes with syntax 1.3.6.1.4.1.1466.115.121.1.34, like  uniqueMember,
the server does not seem to work properly. For example, in my environment, the (uniqueMember=uid=kvaughan,ou=People,dc=example,dc=com)
search filter brings the search result while (uniqueMember=uid=kvaughan, ou=People, dc=example,
dc=com) does not. The only difference here is spaces between RDN components in the search
filter value. Server should normalize uniqueMember values before compare takes place. 

-- 
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

        

Mime
View raw message