Hallvard B Furuseth wrote:
Nope, base64 is just part of LDIF format, which is only relevant on the client side.
OpenLDAP does not support the TeletexString syntax.
LDAPv3 requires all strings to be in UTF-8, so there's no reason for OpenLDAP to support TeletexString syntax.
Such support would be fragile, since there's no unique mapping from LDAPv3's usual UTF-8 character encoding to TeletexString's T.61 character encoding. IRIC there are a bunch of conflicting T.61 encoding variants too.
Still, I don't know why that makes it possible to store such a cert, since certs are binary. You could file an ITS with a request for support, and enclose the cert so there will be something to test it with.
anax writes:
If you base64-encode the string?
suomi
On 2011-07-26 13:39, Vangelis Karatsiolis wrote:
Hi,
while trying to store an attribute with syntax DistinguishedName containing a TeletexString on an OpenLDAP 2.4.23 there are errors in the normalization process and the attribute cannot be stored due to invalid syntax (21). A certificate containing such a subjectDN is also not possible to be stored. Is it possible to deactivate this in this version of OpenLDAP, for example through configuration or during the compilation?