It depends on the definition of the field. userPassword is always base64 encoded.
--Quanah
--On February 6, 2008 2:15:21 PM -0500 "Chris G. Sellers" chris.sellers@nitle.org wrote:
I thought the field was only base64 encoded if it had offending characters such as a space, or something not LDIF compliant?
E.G. you could see an entry that says {crypt}AFDA12321de323
Sellers
On Feb 5, 2008, at 3:08 PM, Quanah Gibson-Mount wrote:
--On February 5, 2008 1:14:35 PM -0600 Pat Riehecky prieheck@iwu.edu wrote:
Strangely they are not prefixed with the {HASHTYPE}.
When I run
ldappasswd -H ldapi:/// -D "cn=testuser,dc=iwu,dc=edu" -w Please -x -s
please
In LDAP I get
userPassword:: cGxlYXNl
What did I do?
You failed to understand the difference between hashes and encoding. userPassword is base-64 encoded. Decode it to see what the actual value is.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
Chris G. Sellers | NITLE - Technology Team 734.661.2318 | chris.sellers@nitle.org AIM: imthewherd | GoogleTalk: cgseller@gmail.com
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration