Data module won't update ldap data
craig.bloodworth - October 6, 2008 - 11:04
| Project: | LDAP integration |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
| Issue tags: | ldapdata |
Jump to:
Description
I'm running drupal 6 with both the ldap integration and the ldap provisioning modules. All was running fine until one day my users couldn't update their profiles or change their passwords. When they attempt to change they get the "The changes have been saved." message however no update is done on the ldap. If an admin tries to change their password they get a massage "The DN uid=test.user,ou=Users,dc=...,dc=...,dc=... is already taken in LDAP." and no update is done on the ldap. Admins can however create users and delete users and changes done to the ldap directly do propagate through to the drupal site. Therefore it seems that the mappings are all OK there is just some problem with the writing back to the ldap. Can anybody help?
#1
What was changed before the first "bad" day? Any drupal or modules updates? Configuration changes? LDAP server changes?
#2
No changes that I can really remember. I think the ldap server itself was locked down however as admins can still add and remove users I don't think that's it. Just in case here's the slapd.conf rules:
access to *
by self write
by users read
by anonymous auth
Anyway the ldap auth configurations are all using the rootdn user and so there should be no access problems.
#3
Syncing of the drupal user data and profile to the LDAP account and back is done by the ldapdata module. So double check it's configuration. Also watchdog entries can show some related information.
#4
Hi, thanks for your continued help. I have checked the configuration and am sure it is OK. I have also checked the watchdog and no entries appear after attempting a profile update. Is there any way to troubleshoot the sync procedure outside of the drupal watchdog?
#5
Do you still have this issue with the dev release?
#6
Closing this issue since got no response from the submitter.