This is an imperfection of back-sql. It doesn't exist any way how to say to slapd, which attributes are base64 encoded.

Here are configuration files, that I am using. Look at "cn", "sn" attributes in "usi.sql" especialy. advanced schemas: http://printer.kn.vutbr.cz/~orim/dbmail.schema http://printer.kn.vutbr.cz/~orim/usi.schema

SQL scripts http://printer.kn.vutbr.cz/~orim/ldap.sql backsql_create.sql http://printer.kn.vutbr.cz/~orim/usi.sql

slapd.conf http://printer.kn.vutbr.cz/~orim/slapd.conf

Hallvard B Furuseth napsal(a):

Please use the mailinglist (openldap-source and -technical) for questions about using the software. This does not look like a bug, which is what the ITS system is for. This ITS will be closed.

Since I'm writing anyway though: Textual attributes in LDAP are as UTF-8. I'm not sure what chacter encoding you are using, but I assume it't something else.

utf-8

As for base64, that's merely part of the LDIF file format, not how the value is represented in LDAP (nor SQL I presume). The '::' after the attribute names tells the client which reads the LDIF to base64-decode the provided value.

It doesn't matter, no LDIF file is imported to back-sql. Record are inserted into MySQL (4 metadata tables).