[courier-users] {CRYPT} with auth_passwd (was: Does auth_passwd work with authldap?)

Lloyd Zusman <ljz@asfast.com> writes:

> [ ... ]
>
> Can anyone tell me what I have to do in slapd.conf (or anywhere else) in
> order to tell my LDAP server that the authldap client is allowed to
> change the password field ... and preferably, in a way that will not
> subsequently break phpldapadmin?

OK, OK ... I found it. I added this to slapd.conf:

access to *
by self write
by anonymous auth
by * read

Now, auth_passwd() works fine, and I can still use phpldapadmin as is.

But this brings up another issue:

When I use auth_passwd(), the new password goes in as a {CRYPT}
password, even though the original password was of type {SSHA}.
Furthermore, in slapd.conf, the following statement exists:

password-hash {SSHA}

So what is causing auth_passwd() to ignore that statement as well as the
original password type, and to store the password as type {CRYPT},
instead?

According to the openldap web site ...

{CRYPT} passwords are supported for migration purposes only. Use
of {SSHA} passwords is recommended.

Is it possible to tell authldap to use the original password type, or at
least the "password-hash" value from slapd.conf, instead of it storing
the new password as type {CRYPT}?

Thanks.


--
Lloyd Zusman
ljz@asfast.com
God bless you.



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users