Hi All,
I want to add usr names which are not in ASCII characters using ldapadd command .
I tried it on RHEL 4.4 , it giving me following error
<error> adding new entry "uid=ああああ,ou=People,dc=avaya,dc=com" ldap_add: Invalid DN syntax (34) additional info: invalid DN </error>
Systems locale set:-*LANG=ja_JP.SJIS*
i googled it i found this
http://www.openldap.org/lists/openldap-software/200308/msg00570.html
But this post is in 2003
So i wanted to know is it LDAP's limitation ?
Thanks in advance
anish patil wrote:
Hi All,
I want to add usr names which are not in ASCII characters using ldapadd command .
I tried it on RHEL 4.4 , it giving me following error
<error> adding new entry "uid=ああああ,ou=People,dc=avaya,dc=com" ldap_add: Invalid DN syntax (34) additional info: invalid DN </error>
Systems locale set:-*LANG=ja_JP.SJIS*
i googled it i found this
http://www.openldap.org/lists/openldap-software/200308/msg00570.html
But this post is in 2003
So i wanted to know is it LDAP's limitation ?
LDAP according to specifications requires to encode strings in UTF-8. So it's not a limitation of LDAP (or of OpenLDAP); you're misusing it.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati@sys-net.it ---------------------------------------
Removed Cc: openldap-devel...
anish patil wrote:
<error> adding new entry "uid=ああああ,ou=People,dc=avaya,dc=com" ldap_add: Invalid DN syntax (34) additional info: invalid DN </error>
Systems locale set:-*LANG=ja_JP.SJIS*
I'm not sure what this locale implies as local charset. Attribute 'uid' is of syntax Directory String.
IMO it's rather an issue with client configuration. How did you provide this input data? Which client you were using? If you use the ldapadd/ldapmodify command-line tool how did you generate the LDIF needed? It MUST contain attribute values of syntax DirectoryString encoded as UTF-8 (or better UTF-8 encoded Unicode wrapped in base64-encoding).
Maybe you could try with a decent GUI-based LDAP client first which has proper handling of charsets?
Ciao, Michael.
Hi,
Thanks for your reply
anish patil wrote:
<error> adding new entry "uid=ああああ,ou=People,dc=avaya,dc=com" ldap_add: Invalid DN syntax (34) additional info: invalid DN </error>
Systems locale set:-*LANG=ja_JP.SJIS*
I'm not sure what this locale implies as local charset. Attribute 'uid' is of syntax Directory String.
IMO it's rather an issue with client configuration. How did you provide this input data? Which client you were using? If you use the ldapadd/ldapmodify command-line tool how did you generate the LDIF needed? It MUST contain attribute values of syntax DirectoryString encoded as UTF-8 (or better UTF-8 encoded Unicode wrapped in base64-encoding).
I am using ldapadd utility which is provided by openladap itself. For that purpose i have created idif file but if i ran file command its output shows that it encoding is different.
<op> $ file test.ldif test.ldif: Non-ISO extended-ASCII text </op>
May be this is the root cause of problem
But due to other reason i do not want to change the encoding of the system.
So their is any way such that it can be work in this conf also?
anish patil wrote:
I am using ldapadd utility which is provided by openladap itself. For that purpose i have created idif file but if i ran file command its output shows that it encoding is different.
<op> $ file test.ldif test.ldif: Non-ISO extended-ASCII text </op>
May be this is the root cause of problem
But due to other reason i do not want to change the encoding of the system.
So their is any way such that it can be work in this conf also?
No. OpenLDAP tools work according to LDAP specs, which mandate strings to be encoded in UTF-8. Either convert your strings, or change tools.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati@sys-net.it ---------------------------------------
anish patil wrote:
I am using ldapadd utility which is provided by openladap itself. For that purpose i have created idif file but if i ran file command its output shows that it encoding is different.
<op> $ file test.ldif test.ldif: Non-ISO extended-ASCII text </op>
This doesn't say much. UTF-8 would be also the same. Consider trying it with a decent GUI LDAP client.
But due to other reason i do not want to change the encoding of the system.
You don't have to. You just have to transcode the data to UTF-8 when generating the LDIF.
Ciao, Michael.
openldap-technical@openldap.org
-
anish patil -
Michael Ströder -
Pierangelo Masarati