directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "andrea (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-491) Export and Re-Import ldif: "invalid password syntax"
Date Wed, 13 May 2009 20:20:45 GMT


andrea commented on DIRSTUDIO-491:


our old directory server is Oracle and we use password encryption  
{crypt}, our future directory server will be  RHDS 8.0 and we will use  
there as password encryption {md5}.  So I used Directory Studio to  
export the user data from OID and import it into RHDS (after removing  
the OID-specific entries) - which causes sometimes this error-message.
Actually, I can't really change the passwords of all those users, so I  
will have to further investigate what's the reason and how to fix it.

Since our passwords are always stored encrypted it seems strange to me  
that RHDS will check them during import. I will continue testing  
tomorrow, at least I now have a clue.

Thank you very much for your help.

w/ kind regards

On May 13, 2009, at 21:24, Stefan Seelmann (JIRA) wrote:

> Export and Re-Import ldif: "invalid password syntax"
> ----------------------------------------------------
>                 Key: DIRSTUDIO-491
>                 URL:
>             Project: Directory Studio
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>         Environment: Windows XP SP2
>            Reporter: andrea
> I export the userdata as ldif, delete all the userdata in the dit and re-import the same
userdata again. Out of  344 entries I get 31 errors:
> #!CONNECTION ldap://xx.xx.xx.xx:636
> #!DATE 2009-05-13T11:27:12.781
> #!ERROR [LDAP: error code 19 - invalid password syntax - password must contain at least
1 digit characters]
> dn: uid=xxxxx,ou=users,ou=posix,o=unixdb
> objectClass: posixaccount
> objectClass: account
> the password might be something like:
> userPassword:: a2NyeXB0fUVtVmh5RWtNUUVwQ0E=
> if I change the "::" to simple ":", I do not have any problem with importing the whole

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message