directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-766) uniqueMember attribute compare does not seem to work properly (uniqueMemberMatch is not implemented?)
Date Tue, 07 Nov 2006 14:04:53 GMT
    [ ] 
Emmanuel Lecharny commented on DIRSERVER-766:

Thanks for the ldif attachment.

I confirm that it is a bug in the server. It seems that the comparizon using DistinguishedNameMatch
does not follow the chapter 4.2.14 of RFC 4517, but is using a simple string comparizon, which
obviously falis if some extra spaces are seen in one of the DN.

Comparizon of such attributes should be done by a comparizon of the number of RDN, the position
of RDNs in the DN, and at the end, by comparing the values.

I will debug the server to figure out a fix for this issue, which is quite serious.

> uniqueMember attribute compare does not seem to work properly (uniqueMemberMatch is not
> -----------------------------------------------------------------------------------------------------
>                 Key: DIRSERVER-766
>                 URL:
>             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, 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:
For more information on JIRA, see:


View raw message