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

Re: Problems with multiple names per OID

--On Thursday, March 03, 2005 9:34 PM +0100 Frank Strauà <strauss@ibr.cs.tu-bs.de> wrote:

I guess this is kind of an FAQ, but I could not find an explanation so
far. If it is an FAQ, maybe someone give me just a pointer to the right

There are several cases where multiple names are defined for a single
OID, e.g. core.schema defines the names "street" and "streetAddress" both
for The Administration Guide says that when attributes are sent
they are labeled with the first name. However, the other names are also
valid in requests. Now the problem is that some LDAP clients send names
in their requests that are known to the LDAP server as "secondary" names,
resulting in responses with other names than the ones in the request.
This results in clients not being able to process the response correctly,
although the requested data is available and even sent back to the client.

Examples are Mozilla Thunderbird and Apple Addressbook which use
different (but only one) names for OID and others.

My personal impression (though I'm new to LDAP, but have quite some
experience with SNMP/SMI, which is also heavily based on ASN.1) is that
LDAP's design is broken in that it does send non-unique labels instead of
unique (and more compact) OIDs in the protocol. But maybe, I'm just
missing a way how to handle the problem correctly.


I file an ITS about this a long time ago, see:


The real problem here is that technically the clients have problems are not following the LDAP specification, and therefore are "broken".


-- Quanah Gibson-Mount Principal Software Developer ITSS/Shared Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin