upgrade to alpha kills ldap authentication.
duran - July 27, 2008 - 22:11
| Project: | LDAP integration |
| Version: | 6.x-1.0-alpha1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
this is on a dev box, so its not the end of the world, but its not a step in the right direction ;)
I just updated to the alpha release, and LDAP login started to fail instantly. There are no helpful error messages on screen, besides asking me if I forgot my password.
how can I help debug/diagnose the problem? Thanks
#1
The same thing happened to me...
I wasn't storing the LDAP passwords on Drupal and I was authenticating 1st with Drupal and afterwards with LDAP
and for some reason...because the user already exists...it might 'think' it's a Drupal user and not a LDAP user
Options:
- Delete users on Drupal if you can
- Authenticate users against LDAP only
I used option 1, because I'm still testing my website and I'm using dummy users at the moment...
but hypothetically, option 2 should work also (I think).
#2
Please provide more information about your configuration. Did you upgraded from D5? Do you use only LDAP authentication or drupal as well, etc...
#3
I was running with mixed mode under 5.8 against AD successfully.
Upgraded to 6.3 and put in 6.x-1.0-alpha1. Anyone who had previously been authenticating by LDAP, not only couldn't authenticate via LDAP but also couldn't log in using Drupal password (mixed mode was selected).
The user "view" page for a previously ldap user did show the ldap authentication section with server and dn, but there was no entry under server and the user "edit" page had no ldap information on it.
I tried removing the ldapauth table, disabling the module, removing the entry from the system table. Didn't seem to have much affect.
#4
Can you try using latest dev version and run the upgrade script?
#5
May be related to #292453: LDAPInterface.php getOption function does not return binddn and bindpw options
#6
Dev from 8/8 seems to fix the authentication problem. However, the section on "existing users" doesn't seem to work.
Choose user conflict resolve procedure: *
Disallow login and log the conflict
Associate local account with the LDAP entry
Pick what should be done if the local drupal account already exists with the same login name.
I have "Associate local account with the LDAP entry" checked, but users who already exist cannot login with their LDAP credentials. I have verified this by deleting a user, creating them in /admin/user/user/create and then trying to login using the ldap credentials. This fails, however, if I delete the user and just attempt to login with ldap credentials, it succeeds and creates the user.
#7
Strange. I have followed the very same steps and user created in drupal could log in with his ldap password.
#8
i have the same problem (#1) after update from ldap_integration-6.1-dev-20080405.tar.gz
to ldap_integration 6.x-1.x-dev (Last updated: August 11, 2008 - 14:06).
after removing all users and the module (with deinstall) an new install the actually dev, it works,
but...
i can not set
- LDAP directory only
- Associate local account with the LDAP entry
- Remove password change fields from user edit form
- Remove email field from form
- Disable email field on form
i can not unset
- Do not store users' passwords during sessions
or the shorter version;)
i can nothing change...
drupal 6.3
saluti
roberto