[Date Prev][Date Next] [Chronological] [Thread] [Top]

case sensibility DN with uniquemember



Since I migrate from V2.0.x to V2.1.x, I have this problem :


search filter ="(uniqueMember=uid=vmathieu,ou=People,ou=Pers,dc=univ-nancy2,dc=fr)"
match 8 entries

search filter = ="(uniqueMember=uid=vmathieu,ou=people,ou=Pers,dc=univ-nancy2,dc=fr)"
match 0 entry

with V2.0.x, the two requests returned the same things, 8 entries.

So , the uniquemenmber attribute is now case sensitive.
Is it normal?

In core.schema, the definition is :

attributetype ( 2.5.4.50 NAME 'uniqueMember'
        DESC 'RFC2256: unique member of a group'
        EQUALITY distinguishedNameMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.34 )

I change temporaly with the next definition, 

attributetype ( 2.5.4.50 NAME 'uniqueMember'
        DESC 'RFC2256: unique member of a group'
        EQUALITY distinguishedNameMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 ) 

How Is'nt a DN search for uniqueMember attribute?

Vincent


-- 
Vincent MATHIEU                 
CRI - Universite NANCY 2            | Email : Vincent.Mathieu@univ-nancy2.fr
Pole Lorrain de Gestion             | Tel   : (33) 03.83.39.64.06
13, Rue Michel Ney - C.O. 75        | Fax   : (33) 03.83.39.64.43
54013 Nancy Cedex.   FRANCE