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

Re: parsing String Representations back into Distinguished Names (ITS#1314)

--On Donnerstag, 6. September 2001 00:00 +0000 Kurt@OpenLDAP.org wrote:

>> o=#46616B756C74C3A474,dc=example,dc=com
> Note that the last string is not equivalent to the
> first two and likely is invalid.  The # must be
> followed by the base64 encoding of the BER encoding
> of the value, a directoryString (presumably of CHOICE
> universalString).

You're right, exept that according to RFC2253 it must be hex encoded:
   If the AttributeValue is of a type which does not have a string
   representation defined for it, then it is simply encoded as an
   octothorpe character ('#' ASCII 35) followed by the hexadecimal
   representation of each of the bytes of the BER encoding of the X.500
Since there IS an string representation for "o", the server probably does 
not need to support/transliterate such a DN anyway.

Norbert Klasen
DAASI International GmbH                 phone: +49 7071 29 70336
Wilhelmstr. 106                          fax:   +49 7071 29 5114
72074 Tübingen                           email: norbert.klasen@daasi.de
Germany                                  web:   http://www.daasi.de