Hi,
On drupal.7.19 and Ldap 7.x-2.x-dev released on 2013.01.28.
I have ldap authentication working(so provisioning and synching from LDAP to Drupal works) and configured ldap-user module, so it should solve the provisioning and synching in the other direction(to LDAP).
My usecase:
-From LDAP to Drupal prov. and synch, when a user authenticates(logs in) <- this works
-From Drupal to LDAP: if a user use the "sign on" form on drupal page, an ldap entry will be created(after admin unblock the user)<- this works too , but
-- on updateing a user profile, it does not synch to ldap. I have tested it on admin/config/people/ldap/user/test and i dont understand what does the "false" mean, i marked it on the screenshot.
http://drupal.org/files/LDAP_user_test_0.png
Theres no debugging info. What is the difference between fall 1 and 2?
thx for help
Comment | File | Size | Author |
---|---|---|---|
LDAP_user_test.png | 145.59 KB | Laz5530 |
Comments
Comment #1
Laz5530 CreditAttribution: Laz5530 commentedOn what depends if i can edit the 'password' and for example 'First Name' from ldap associated in drupal?
Sometimes it can be edited and will be written in ldap
sometimes it can be edited but after 'submit' it doesnt change
and sometimes it is simply blended out(the whole field is gray).
Could somebody tell me why? I cant believe that im the only one having this problem.
Comment #2
synth3tk CreditAttribution: synth3tk commentedYou're not the only one. It's probably related to #1884922: LDAP User: Password field disabled Makes use case of Provisioning Passwords from Drupal to LDAP unusable.
Comment #3
johnbarclay CreditAttribution: johnbarclay commentedreading through the ldap_user.test_form.inc code indicates "false" means the synch action is enabled and configured to happen, but
$ldap_user_conf->synchToDrupalAccount(NULL, $user_edit, NULL, $test_query);
is returning false.I suspect the issue is in admin/config/people/ldap/user in the "Provisioning from Drupal to LDAP Mapppings:" section. To debug, simply uncheck all but the simplest field in "On synch to ldap entry" column and test. If its the password field that is causing the problem, #2 is likely the issue.
Comment #4
johnbarclay CreditAttribution: johnbarclay commentedPlease try to replicate with the current 7.x-2.x-dev. A number of synch and provision to ldap issues were fixed. But I don't want to lump them all together. In your comments here, please be clear about when you are synching and provisioning to LDAP.
Comment #5
johnbarclay CreditAttribution: johnbarclay commentedClosing for lack of clarity. On any synch issues please try to narrow down to particular fields or errors thrown. These sound password related.