Hi

I have a user who successfully auth'ed against ldap last week. Then this week he had his password changed on the ldap server, and now can't auth using the ldap module. Looking at his password in phpmyadmin, the md5 hash is neither his new password or his old password.
With this problem, I thought if I change his password to the new one, then change his account so that it's drupal auth'ed instead of ldap he would be able to login. Not so. drupal is still trying to authenticate his account against ldap.

Is this because his username is an ldap username, or is it something to do with the data field in the users table? (I notice the data field has quite a few ldap_ vars in it).

I would have thought that ticking the box to disable ldap auth in his profile would tell the ldap module to use drupal auth instead of still trying to check the ldap server?

Cheers for any help with this

Comments

fronbow’s picture

fronbow commented

If I delete the contents of the data field in the users table, the user can login in okay.
But it appears as though regardless of what settings you change, if there's anything in the data field, it gets used instead of obeying the "Authenticate via LDAP" checkbox in the users' profile.

Is this normal behaviour? it would mean if I (or anyone else) had this problem again, I would have to go into phpmyadmin to empty the data field, which seems a bit much?!

cheers

johnbarclay’s picture

johnbarclay commented
Status: Active » Closed (won't fix)

Closing 5.x issues to clean out issue queue.