Quanah Gibson-Mount wrote:
--On Tuesday, December 15, 2009 12:52 AM +0100 Zdenek Styblik stybla@turnovfree.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
let's open up old wounds. Ok, it sounds jerky, but I don't mean it.
Why not just issue a password change operation and let the OpenLDAP server use its default encryption mechanism that the admin has specified?
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
As I've explained later, I didn't figure it out/found out how to use such feature nor I'm aware such feature exists. I'll be more than happy to use it. Or I don't know if I did something wrong. Could you please provide some example in case it's different from:
--- SNIP --- changetype: modify userPassword: mySecretPasswd --- SNIP ---
where 'mySecretPasswd' is in clear text and LDAP is supposed to know what to do exactly with userPassword. In another words, get default password encryption, generate hash, store password.
At least I think I did it like this. I don't recall correctly, as it was wrong way do change password and since then I'm using % slappasswd; to get hash when in command-line or function in application[s].
Thanks, Zdenek