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

Re: problems with exporting/iimporting passwords

Hi there,
problem solved ! it was my mistake, I didnt pay attention, that some passwords consist of more than one line,
must be a base64 thing, that after some character comes a new line (wikipedia says so) - and my bash-script ignored (and still does :-) ) second line



-------- Original-Nachricht --------
> Datum: Tue, 18 Nov 2008 22:59:11 +0100
> Von: thom_schu@gmx.de
> An: openldap-software@openldap.org
> Betreff: problems with exporting/iimporting passwords

> Hi everybody,
> we are installing a new ldap-server, because we need a new structure.
> so a simple export/import via slapcat/slapadd is not possible, because we
> need to change the object structure.
> I wrote a bash shell-script (we are working under suse), which exports the
> user datas via ldapsearch, builds
> the new objects and saves it in ldif-format. then I import the ldif-file
> via ldap-add in the new ldap-server.
> but when I want to import the ldif-file, ldapadd complains about 50 users
> (from 900 total), that they woud have an invalid format -  the lines, which
> are invalid are always the userPassword-lines of this user.
> I tried already to extract this lines with slapcat, copied the extracted
> lines into my ldif-file, but still the same error.
> Is there any other way to export/import the password ? can it be a
> char-set problem ? I really dont know anymore, 
> what else I could do.....
> thanks
> gizmo
> -- 
> Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
> http://www.gmx.net/de/go/multimessenger

Sensationsangebot nur bis 30.11: GMX FreeDSL - Telefonanschluss + DSL 
für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a