Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Authorization: Duplicate entry in modules/user/user.module
» Authentication: Duplicate entry in modules/user/user.module
Category:
bug
» support
Status:
Active
» Closed (duplicate)
Sorry about this. No one has taken an interest in coding an upgrade path for d6 ldap_integration to d7 ldap. Aside from moving settings over, I believe upgrade code would take each user's db record and adjust it as well as any authmap entries.
Thank you very much, johnbarclay, for your stop gap. It helped me transition from shibboleth to ldap. Users could not login using ldap because shibboleth had already inserted them into the authmap table. I ran this query and all was good: delete from authmap where module = 'shib_auth';
Comments
Comment #1
johnbarclay CreditAttribution: johnbarclay commentedSorry about this. No one has taken an interest in coding an upgrade path for d6 ldap_integration to d7 ldap. Aside from moving settings over, I believe upgrade code would take each user's db record and adjust it as well as any authmap entries.
This is a duplicate of issue #1023016: upgrade hook or migrate function for ldapauth and ldapgroups
A stop gap measure might be code to remove ldap_integration data and convert it to ldap data structure when a user authenticates.
For your case, you might just clear out the ldap entries in the authmap table with
DELETE FROM authmap WHERE module = 'ldapauth'
Comment #2
Higarigh CreditAttribution: Higarigh commentedThis was the solutuion. Thank you very much !! ;D
Comment #3
msac CreditAttribution: msac commentedThank you very much, johnbarclay, for your stop gap. It helped me transition from shibboleth to ldap. Users could not login using ldap because shibboleth had already inserted them into the authmap table. I ran this query and all was good:
delete from authmap where module = 'shib_auth';