[I tried searching the docs for the answer without much luck, so apologies if I've missed it] Does openldap (2.4.26) support DNs containing utf8 multi-byte characters? e.g. a DN containing é like cn=été,dc=a,dc=b ? If not, what's the recommended way of handling such DNs? Chris
On 24.11.2011 18:14, Chris Card wrote:
[I tried searching the docs for the answer without much luck, so apologies if I've missed it] Does openldap (2.4.26) support DNs containing utf8 multi-byte characters? e.g. a DN containing é like cn=été,dc=a,dc=b ? If not, what's the recommended way of handling such DNs? Chris
Take a look at RFC 4514 (*http://www.ietf.org/rfc/rfc4514.txt?number=2253*) (Page 4 should be your answer)
[I tried searching the docs for the answer without much luck, so apologies if I've missed it] Does openldap (2.4.26) support DNs containing utf8 multi-byte characters? e.g. a DN containing é like cn=été,dc=a,dc=b ? If not, what's the recommended way of handling such DNs? Chris
Take a look at RFC 4514 (http://www.ietf.org/rfc/rfc4514.txt?number=2253) (Page 4 should be your answer)
I've tried that but I get an invalid DN error back from slapd (and the slapdn program) if I replace é by \c3\a9 in the DN. Chris
[I tried searching the docs for the answer without much luck, so apologies if I've missed it] Does openldap (2.4.26) support DNs containing utf8 multi-byte characters? e.g. a DN containing é like cn=été,dc=a,dc=b ? If not, what's the recommended way of handling such DNs? Chris
Take a look at RFC 4514 (http://www.ietf.org/rfc/rfc4514.txt?number=2253) (Page 4 should be your answer)
I've tried that but I get an invalid DN error back from slapd (and the slapdn program) if I replace é by \c3\a9 in the DN.
slapdn -f testrun/slapd.1.conf 'cn=\c3\a9' DN: <cn=\c3\a9> check succeeded normalized: <cn=é> pretty: <cn=é>
git master of 10 minutes ago; what version are you using?
p.
Chris
[I tried searching the docs for the answer without much luck, so apologies if I've missed it] Does openldap (2.4.26) support DNs containing utf8 multi-byte characters? e.g. a DN containing é like cn=été,dc=a,dc=b ? If not, what's the recommended way of handling such DNs? Chris
Take a look at RFC 4514 (http://www.ietf.org/rfc/rfc4514.txt?number=2253) (Page 4 should be your answer)
I've tried that but I get an invalid DN error back from slapd (and the slapdn program) if I replace é by \c3\a9 in the DN.
slapdn -f testrun/slapd.1.conf 'cn=\c3\a9' DN: <cn=\c3\a9> check succeeded normalized: <cn=é> pretty: <cn=é>
git master of 10 minutes ago; what version are you using?
2.4.26 + some sssvlv.c patchesIs there something in the config or schema that controls this? Chris
[I tried searching the docs for the answer without much luck, so apologies if I've missed it] Does openldap (2.4.26) support DNs containing utf8 multi-byte characters? e.g. a DN containing é like cn=été,dc=a,dc=b ? If not, what's the recommended way of handling such DNs? Chris
Take a look at RFC 4514 (http://www.ietf.org/rfc/rfc4514.txt?number=2253) (Page 4 should be your answer)
I've tried that but I get an invalid DN error back from slapd (and the slapdn program) if I replace é by \c3\a9 in the DN.
slapdn -f testrun/slapd.1.conf 'cn=\c3\a9' DN: <cn=\c3\a9> check succeeded normalized: <cn=é> pretty: <cn=é>
git master of 10 minutes ago; what version are you using?
2.4.26 + some sssvlv.c patchesIs there something in the config or schema that controls this? Chris
So an example: slapdn -v -F *********/slapd.d 'mail=\c3\98U,dc=x,dc=y'DN: <mail=\c3\98U,dc=x,dc=y> check failed 21 (Invalid syntax) are there any changes that might affect this? Chris
Chris Card wrote:
So an example: slapdn -v -F *********/slapd.d 'mail=\c3\98U,dc=x,dc=y'DN: <mail=\c3\98U,dc=x,dc=y> check failed 21 (Invalid syntax) are there any changes that might affect this?
I guess this fails because attribute type 'mail' has LDAP syntax IA5String which does not allow NON-ASCII chars. OpenLDAP does syntax checking of all DN components.
Ciao, Michael.
Chris Card wrote:
So an example: slapdn -v -F *********/slapd.d 'mail=\c3\98U,dc=x,dc=y'DN: <mail=\c3\98U,dc=x,dc=y> check failed 21 (Invalid syntax) are there any changes that might affect this?
I guess this fails because attribute type 'mail' has LDAP syntax IA5String which does not allow NON-ASCII chars. OpenLDAP does syntax checking of all DN components.
Ciao, Michael.
Thanks, that's it. Chris
openldap-technical@openldap.org
-
Chris Card -
masarati＠aero.polimi.it -
Michael Ströder -
Raffael Sahli