This is almost a bug report since the behavior when LDAP_FIRST_DRUPAL is enabled causes a password that is changed on the LDAP server or an account that is disabled on the LDAP server to be ignored by DRUPAL since that user has had an independant DRUPAL account created with the old password. Thus...
I think it would be useful to many sites to have a setting to enable the following behavior in ldapauth.module:
1. If an LDAP account exists for the given username, use it instead of the matching DRUPAL account.
2. If an LDAP account does NOT exist, and a DRUPAL account DOES, then use that.
This allows for a site that is primarily LDAP-based, but can have some non-LDAP accounts in their DRUPAL site if they want to.
I added a one-line patch to our ldapauth.module file to implement this (without any setting to turn it on or off though) This line is added to the "_ldapauth_is_ldap_login_only" function before the "return" statement:
if (_ldapauth_user_lookup($name)) { return true; }
Comments
Comment #1
kreaper commentedCan you d/l the 5.x module and see if it meets your needs ?
kreaper
Comment #2
kreaper commentedComment #3
johnbarclay commentedClosing 4.7 issues to clean out issue queue.