> >>If so, what changes will be required to our setup? > > > >It depends exactly on what "encrypted passwords" means. It could mean > >any one of different things. > > > >1) LDAP connection using SSL > > > >2) Encrypted passwords held in the userPassword attribute, which will > >be accessible to the admin login courier-authlib uses to bind. > > > >3) Encrypted passwords held in the userPassword attribute, not > >accessible. > > > >Depending on what your story is, different configuration changes will > >be required. > > In regards to a vanilla a eDirectory setup, it's #3 (and #1, but that's > irrelevant), eDirectory's passwords default are one way, there is > absolutely no way to pull the password (or even the hash) out via LDAP.
Then you can probably use LDAP_AUTHBIND to validate the passwords. However this will only let you use AUTH PLAIN, not CRAM-MD5 (which in any case is not a problem if users are connecting in over SSL) ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
