From: Philippe DUBY <duby@asi.fr> > - When I add a password with $entry->{userpassword} = [$sha_pass];, the > password seems entered correctly, but if I export it in LDIF format, the > userpassword entry does not begins with {SHA}... but seems encoded. Do > you have a solution to correct this ? Are you included {SHA} at the beginning of the $sha_pass string? The directory server does not do that automatically when you "manually" change the password like this (I think). # Yes, $sha_passwd looks like "{SHA}base64_code" So there is someone during the add process which encode again the data !

Example : Sent : $entry->{userpassword} = "{SHA}Wa5kP3m+TLHELe0wK3n02DNSOI4="; LDIF Export : userpassword:: e1NIQX1XYTVrUDNtK1RMSEVMZTB3SzNuMDJETlNPSTQ9Cg==

Setting all current Open/Normal to M4.

Clearing "M" field since Directory product is not used for 5.0 specific project bug metrics and will mess up our queries on milestones.

This bug has not been touched for more than nine months. In most cases, that means it has "slipped through the net". Please could the owner take a moment to add a comment to the bug with current status, and/or close it. Thank you :-) Gerv

ping

Hmmm, this works fine for me, maybe it's an LDAP server setting? thor (17:58) 478/0 $ ./examples/modattr.pl -b o=ogre.com -h localhost -D cn=manager,o=ogre.com -w foofoo userPassword="{SSHA}Pxm2o5RbgVP6WpQCpiiVejj6Fw+M7/hY" uid=leif thor (17:59) 479/0 $ examples/qsearch.pl -b o=ogre.com -h localhost uid=leif Searched for `uid=leif': dn: uid=leif,ou=people,o=ogre.com objectclass: inetOrgPerson uid: leif givenname: Leif sn: Hedstrom cn: Leif Hedstrom userpassword: {SSHA}Pxm2o5RbgVP6WpQCpiiVejj6Fw+M7/hY