This is a discussion on [courier-users] Re: Does auth_passwd work with authldap? within the Courier-Imap forums, part of the Mail Servers and Related category; This is a MIME GnuPG-signed message. If you see this text, it means that your E-mail or Usenet ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages. The Internet standard for MIME PGP messages, RFC 2015, was published in 1996. To open this message correctly you will need to install E-mail or Usenet software that supports modern Internet standards. --=_mimegpg-commodore.email-scan.com-14988-1137450198-0003 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Lloyd Zusman writes: > Sam Varshavchik <mrsam@courier-mta.com> writes: > >> Lloyd Zusman writes: >> >>> And finally, the LDAP_BINDDN and LDAP_BINDPW values are indeed set >>> properly in authldaprc. >>> Is there some sort of authldap configuration option that's necessary >>> in order for auth_passwd() to function properly? Or ... ??? >> >> No. I would suggest setting DEBUG_LOGIN=2 in authdaemond, and see what >> gets logged. Although there are no debug messages in the code, at the >> moment, that log what happens during a password change attempt, at least >> you'll be logging what happens during authentication. > > Thanks. OK I did that, and when I made the password change attempt, I > got this error in syslog: > > Jan 16 16:59:51 authdaemond: LDAP modify failed: Insufficient access > > Everything else that came prior to that was the logging of a successful > operation. > > Does anyone know what I have to do in order to give authdaemond/authldap > sufficient access to modify the database? This looks like access controls on your LDAP server. You need to tell your LDAP server that this client is allowed to change the password field. You're all set on the Courier side. You need to fix up the LDAP server side. --=_mimegpg-commodore.email-scan.com-14988-1137450198-0003 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQBDzBzWx9p3GYHlUOIRAuiwAJwJ5irApim2t39DbxpUpm lLj4+6wQCffFbK QUHDEus9iF/v9Sc6YFkkSXo= =D2UF -----END PGP SIGNATURE----- --=_mimegpg-commodore.email-scan.com-14988-1137450198-0003-- ------------------------------------------------------- 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 |