Hi, While working with OpenLDAP, I've observed something strange. I am not sure if this is the anticipated behaviour. Let us say we have two attributes 'name' and 'middleName' and the former is the superior of the latter i.e.
attributetype ( 1.3.6.1.4.74 NAME 'middleName' SUP name )
Now let us assume that the value of the attribute 'middleName' for a particular dn is 'Konda'. Then performing a search on the basedn with the filter "(name=Konda)" returns that particular dn. Is this a bug or anticipated behaviour?
Regards, Rahul.
Rahul Amaram writes:
attributetype ( 1.3.6.1.4.74 NAME 'middleName' SUP name )
Now let us assume that the value of the attribute 'middleName' for a particular dn is 'Konda'. Then performing a search on the basedn with the filter "(name=Konda)" returns that particular dn. Is this a bug or anticipated behaviour?
It's a feature, not a bug. Just like filter (title=foo) will match attribute "title;lang-en: foo". See RFC 4511 section 4.5.1.7, which refers to matches of "the attribute type or subtype".
Similarly, if 'name' is listed as one of the attributes to be returned, 'middleName' will be returned. And cn, sn, title, givenName.
Rahul Amaram wrote:
While working with OpenLDAP, I've observed something strange. I am not sure if this is the anticipated behaviour. Let us say we have two attributes 'name' and 'middleName' and the former is the superior of the latter i.e.
attributetype ( 1.3.6.1.4.74 NAME 'middleName' SUP name )
Now let us assume that the value of the attribute 'middleName' for a particular dn is 'Konda'. Then performing a search on the basedn with the filter "(name=Konda)" returns that particular dn. Is this a bug or anticipated behaviour?
This works as intended. If you don't want that then don't use SUP name.
Ciao, Michael.
Thanks for the quick reply.
Regards, Rahul.
Michael Ströder wrote:
Rahul Amaram wrote:
While working with OpenLDAP, I've observed something strange. I am not sure if this is the anticipated behaviour. Let us say we have two attributes 'name' and 'middleName' and the former is the superior of the latter i.e.
attributetype ( 1.3.6.1.4.74 NAME 'middleName' SUP name )
Now let us assume that the value of the attribute 'middleName' for a particular dn is 'Konda'. Then performing a search on the basedn with the filter "(name=Konda)" returns that particular dn. Is this a bug or anticipated behaviour?
This works as intended. If you don't want that then don't use SUP name.
Ciao, Michael.
-
Hallvard B Furuseth -
Michael Ströder -
Rahul Amaram