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

Re: OpenLDAP 2.0.6 -> 2.0.7 problem (ITS#890)



Hello!

> I think you used to have your special characters coded as ISO 8859-1.
> You cannot do that, they have to be in UTF-8 (an encoding of Unicode
> and ISO-10646).

The umlauts are normal ISO 8859-1 (ISO Latin 1) characters.

> > And how can I fix this problem to be able to import my old
> > directory-data?
> Sorry, I think you will have to translate them.  And your old
> applications will have to be reconfigured for UTF-8.

attributetype ( 2.5.4.3 NAME ( 'cn' 'commonName' ) SUP name )
attributetype ( 2.5.4.4 NAME ( 'sn' 'surname' ) SUP name )
attributetype ( 2.5.4.41 NAME 'name'
        EQUALITY caseIgnoreMatch
        SUBSTR caseIgnoreSubstringsMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} )

This Syntax is according to the documentation an UTF-8 string. So it looks
like I've to convert it. But there is too much data for a manual
conversion. Is there a tool available to convert LDIF-Data from
ISO-LATIN-1 to UTF-8? And there is an additional Problem: The attributes
containing ISO-LATIN-1 characers are "binary" encoded in the LDIF-Data
(for example cn:: S2xhdXMgVHL2bmRsZQ==). This data should be correctly 
converted to UTF-8. But the attribute userpassword looks like it is an
normal octet string:

attributetype ( 2.5.4.35 NAME 'userPassword'
        EQUALITY octetStringMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.40{128} )

I suppose if this data is also converted to UTF-8, this will break the
userauthentication because. So the tool should leave the
userpassword-attribute untouched. Has somebody a solution or tip?

Daniel