[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: openldap 2.2.x

You may try this instead:

postalAddress:: TmllZGVyc8OkY2hzaXNjaGVzIExhbmRlc2FtdCBmw7xyIFZlcmJyYXVjaGVyc2No

This is UTF-8 encoded (required by RFC4519+RFC4517).

2012/11/2 PÃrschke, Gunnar <gunnar.poerschke@bvl.bund.de>:
> With my ldap client, JXplore, I import a subtree and get this error message:
> [LDAP: error code 21 - postalAddress: value #0 invalid per syntax];
> remaining name
> 'uid=reskes@circa,ou=Users,ou=DATA,ou=fis-vl.bund.de,o=IRCusers,l=CIRCA'
> The import job fails (same result with slapadd).
> This are the data:
> postalAddress:: TmllZGVyc+RjaHNpc2NoZXMgTGFuZGVzYW10IGb8ciBWZXJicmF1Y2hlcnNj
>  aHV0eiB1bmQgTGViZW5zbWl0dGVsc2ljaGVyaGVpdCwgRGV6ZXJuYXQgMjMsIFBvc3RmYWNoIDM
>  5NDksIDI2MDI5IE9sZGVuYnVyZw==
> -----UrsprÃngliche Nachricht-----
> Von: PÃrschke, Gunnar
> Gesendet: Donnerstag, 1. November 2012 13:51
> An: 'openldap-technical@openldap.org'
> Betreff: openldap 2.2.x
> Hi all,
> we have an very old openldap running and we need to migrate data to latest
> openldap version. I create an ldif but the data in that file are encoded
> "base64". Is there a trick to disable that? My plan is to export everything
> from openldap 2.2 database (lbdb) without base64 encoding so I can easily
> use slapadd to add this data to a database on my new openldap 2.4.2x system
> Thank you for any idea.
> Gunnar