[jira] Closed: (DIRSERVER-766) uniqueMember attribute compare does not seem to work properly (uniqueMemberMatch is not implemented?)

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

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

Emmanuel Lecharny closed DIRSERVER-766.
---------------------------------------


closed

> uniqueMember attribute compare does not seem to work properly (uniqueMemberMatch is not implemented?)
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-766
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-766
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>         Environment: Windows XP SP2, Java 1.5.06
>            Reporter: Kirill Kovalenko
>            Assignee: Emmanuel Lecharny
>             Fix For: 1.5.1
>
>         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.
-
You can reply to this email to add a comment to the issue online.