7:28 a.m.
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(a)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(a)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
7:53 a.m.
On Fri, 2 Nov 2012, Pörschke, Gunnar wrote:
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(a)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==
RFC 4517 defines the Postal Address syntax as requiring the value to
encoded in valid UTF-8, but that value appears to be encoded in some
ISO-8851 variant. You'll need to reencode the value...and then verify
that any applications reading that value handle it correctly.
Philip Guenther
7:57 a.m.
New subject: openldap 2.2.x
You may try this instead:
postalAddress:: TmllZGVyc8OkY2hzaXNjaGVzIExhbmRlc2FtdCBmw7xyIFZlcmJyYXVjaGVyc2No
dXR6IHVuZCBMZWJlbnNtaXR0ZWxzaWNoZXJoZWl0LCBEZXplcm5hdCAyMywgUG9z
dGZhY2ggMzk0OSwgMjYwMjkgT2xkZW5idXJn
This is UTF-8 encoded (required by RFC4519+RFC4517).
2012/11/2 Pörschke, Gunnar <gunnar.poerschke(a)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(a)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(a)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
--
Erwann.
4049
days inactive
4049
days old
openldap-technical@openldap.org
2 comments
3 participants
participants (3)
-
Erwann Abalea -
Philip Guenther -
Pörschke, Gunnar