[
https://issues.apache.org/jira/browse/DIRSERVER-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-766.
-----------------------------------------
Resolution: Fixed
Fixed ! And also fixed a bug in the associated SyntaxChecker.
http://svn.apache.org/viewvc?rev=569405&view=rev
http://svn.apache.org/viewvc?rev=569435&view=rev
http://svn.apache.org/viewvc?rev=569436&view=rev
http://svn.apache.org/viewvc?rev=569437&view=rev
http://svn.apache.org/viewvc?rev=569565&view=rev
http://svn.apache.org/viewvc?rev=569569&view=rev
http://svn.apache.org/viewvc?rev=569570&view=rev
http://svn.apache.org/viewvc?rev=569579&view=rev
http://svn.apache.org/viewvc?rev=569580&view=rev
> 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.
