Just found out what was wrong. The code was also propagating the displayName value to gecos. We used gecos as an extra copy of displayName because of one client application which only did work with gecos.
The error wasn't noticed before because now for the first time we had a user with an umlaut in his name. We could just remove gecos from the directory altogether because the program in question isn't in use any more.
But isn't a gecos value supposed to hold a full name? It being unable to hold an utf8 value seems somehow wrong, no?
Regards,
yvan
yvan vander sanden wrote:
But isn't a gecos value supposed to hold a full name? It being unable to hold an utf8 value seems somehow wrong, no?
Attribute type 'gecos' is declared with LDAP syntax IA5String. Therefore you cannot store NON-ASCII chars in there.
Ciao, Michael.
openldap-technical@openldap.org