Re: Compare on DNs is sometimes incorrect (ITS#282)

[Kurt@OpenLDAP.org]

At 03:57 PM 9/9/99 GMT, dave@rudedog.org wrote:
>Full_Name: Dave Carrigan
>Version: 1.2.6
>OS: Linux
>URL: 
>Submission from: (NULL) (216.39.144.181)
>
>
>Assume the following groupOfUniqueNames:
>
> dn: cn=The Group, o=Airius.com
> objectclass: top
> objectclass: groupOfUniqueNames
> cn: The Group
> uniqueMember: uid= carter, o=Airius.com
>
>Now, assume I call
>
>  ldap_compare_s(ldap, "cn=The Group, o=Airius.com", 
>                       "uniquemember", "uid=carter, o=Airius.com") 
>
>This returns LDAP_COMPARE_FALSE. It should return LDAP_COMPARE_TRUE, because in
>
>LDAPv2, the DNs "uid=carter, o=Airius.com" and "uid= carter, o=Airius.com" are 
>equivalent.

Attributes are only compared as DNs if the attribute type is known to
contain DNs.  It's likely you have not specify a syntax for "uniquemember"
and it defaulted to case ignore string.

Please add:
	attribute uniquemember dn

to your local schema configuration file.

Kurt