You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2006/11/07 15:00:53 UTC
[jira] Assigned: (DIRSERVER-766) uniqueMember attribute compare
does not seem to work properly (uniqueMemberMatch is not implemented?)
[ http://issues.apache.org/jira/browse/DIRSERVER-766?page=all ]
Emmanuel Lecharny reassigned DIRSERVER-766:
-------------------------------------------
Assignee: Emmanuel Lecharny
> 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
> Assigned To: Emmanuel Lecharny
> 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