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.Hi,
I am able to create user account in LDAP, and also able to sync from LDAP to drupal, but drupal to LDAP sync not working!.
when i edit a user profile and save it the changes wont take effect although it says "The changes have been saved" but its not reflected in LDAP and the form loads the old value only.
The error i get in Drupal log is:
"LDAP entry on server apps1 not synched because error. username=myname, uid=4448"
is this a bug..?
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | devel_result.png | 18.8 KB | madhusudan |
| #6 | Drupal_to_LDAP_settings-new.png | 55.95 KB | madhusudan |
| #6 | LDAP_to_drupal-mapping.png | 74.17 KB | madhusudan |
Comments
Comment #1
recrit CreditAttribution: recrit commentedtry the patch at #2024683: Stop triple provisioning to Drupal on user create to see if it fixes your issue
Comment #2
madhusudan CreditAttribution: madhusudan commented^ @recrit Thanks for the patch.
But still gives same error!!.
update:
tried another patch https://drupal.org/node/1989018 (the last one), and started tracing error and outputting the ldap arrays with print_r, found that proposed_ldap_entry array doesn't contain "dn"!.
now I have to check why dn is not coming in array
Comment #3
madhusudan CreditAttribution: madhusudan commentedcan anyone help me..?
this is the watchdog error. I added dn and server in watchdog and it shows 'dn' empty!!.
"LDAP entry on server apps1 not synched because error. username=username, uid=4303, dn=, server=localhost ".
we are migrating from D6 to D7 and its holding all our migration process.
any idea why dn is not showing up..?
Comment #4
madhusudan CreditAttribution: madhusudan commentedgot the root cause..
In LDAP User Settings under "Provisioning from Drupal to LDAP Mappings" in Target LDAP Token
"On Synch to LDAP Entry" was not checked for [dn] .
although it is not necessary for dn to be synched every time. this has become a mandatory to sync other attributes, which is not fair!.
if it is optional it must be optional.
can anyone fix this and update to the latest version.
Comment #5
larowlanno update for > 12 months - closing
Comment #6
madhusudan CreditAttribution: madhusudan commentedHi
Looks like the issue is still there even if i tick On Synch to LDAP Entry" for [dn] , not able to update any user fields to LDAP, password field is visible, and account creation to LDAP works correctly, Attached are my settings and devel output.
I am using 389 Directory server in Ubuntu 14.04.
Am i missing something..? please let us know.
Comment #7
grahlComment #8
grahlI moved this over to bug reports earlier in the year but after reviewing this but don't really see an issue here, syncing DN should make it work. However, I'd added this ticket to improve on this UX issue: #2924733: Add fixed DN field to Provision-to-LDAP mappings.
For the issue madhusudan is experiencing this is however insufficient information to provide additional help. The function doing the modification modifyLdapEntry() should provide additional debugging messages which are not available. This should definitely be called with dn set. Would you be able to set a breakpoint within modifyLdapEntry() and drupalUserToLdapEntry() to provide some context?
Comment #9
smalltree CreditAttribution: smalltree commentedI'm having the same issue. With the latest version: 7.x-2.3
Made changes to user profile, but not get saved in LDAP (My case: Active Directory)
It was working before, but somehow, it's not working anymore.
Any help would be appreciated.
Comment #10
grahl@smalltree: Without additional information from you it's impossible to determine where your configuration is faulty now.
Comment #11
grahlI'm closing this issue due to no additional feedback from the involved participants.
Please create new support requests if you encounter a current issue and reference this one, if you believe there is some overlap.