[Date Prev][Date Next]
Re: extended characterset/binary/base64 support
Naufal Sheikh <firstname.lastname@example.org> writes:
> ok, so what are my options here. I am very new at ldap, and am doing this migration by installing the
> software and copying the config files. Is there any module or library which needs to be installed to get
> this resolved, because this thing is working on the current production system. If you can just point me
> to the right direction..
> On 10/25/07, Dieter Kluenter <email@example.com> wrote:
> "Dieter Kluenter" <firstname.lastname@example.org> writes:
> > "Naufal Sheikh" <email@example.com > writes:
> >> I have been trying to redo everything from the beginning, and now I
> >> have got everything right except the same problem. Here is the error
> >> which slapadd generates:
> >>>>> dnPrettyNormal: <uid=ddmartin,o=trac>
> >> <<< dnPrettyNormal: <uid=ddmartin,o=trac>, <uid=ddmartin,o=trac>
> >> str2entry: invalid value for attribute clientorg (syntax
> >> 184.108.40.206.4.1.14220.127.116.11.15)
> >> slapadd: could not parse entry (line=102853)
> >> clientorg:: TXVzc2VsaGH8cyBQcm9kdWN0aW9ucw==
> 'Musselhaï Productions', there is a strange character in
> > the value.
As I mentioned already the attribute value of clientorg is somehow
corrupted or contains a character that is not valid in accordance with
the syntax description of directory string. For more information on
directory string syntax see RFC 4517 section 3.6, RFC 4512 section 1.4
and RFC 3629.
just reenter the correct value and you are done.
Dieter KlÃnter | Systemberatung
GPG Key ID:8EF7B6C6