Closed (fixed)
Project:
Lightweight Directory Access Protocol
Version:
8.x-3.0-alpha2
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
13 Jan 2017 at 14:04 UTC
Updated:
2 Mar 2017 at 14:13 UTC
Jump to comment: Most recent
Comments
Comment #2
plingamn commentedComment #3
timwoodIssue formatting.
Comment #4
plingamn commentedComment #5
plingamn commentedComment #6
timwoodChanged version in version field.
Comment #7
grahlHi
As long as you have mixed authentication enabled you should be able to use Drupal's authentication as well as LDAP side-by-side and the match is opportunistic, i.e., if you use the password reset function for a user he or she can receive a new password and it doesn't have to match your AD.
Also, you should be able to update your user's data in the directory as long as you have configured the relevant field mapping under "Provisioning to LDAP", though I personally don't have such a setup running.
Comment #8
plingamn commentedHello grahl,
Thank you very much for the insight .. Will work on the field mapping under "Provisioning to LDAP" and see if something can be done.
I really appreciate all your help ..
--
Thank you
Prashanth
Comment #9
timwoodHey grahl,
So does that mean that this LDAP suite of modules doesn't support LDAP password management/maintenance at all while in exclusive mode?
I thought the old D6 implementation, using the https://www.drupal.org/project/ldap_integration module supported password manage in the LDAP, but we may have created custom code to do that.
Thanks
Comment #10
grahlWill respond next week
Comment #11
plingamn commentedHello grahl,
Any update on the AD password update from the ldap module
--
Thanks
Prashanth
Comment #12
grahlHi timwood
Yes, at the moment you'd need to write custom code. Here's the documentation for exclusive mode in Drupal 7 on which 8 is based:
Only LDAP Authentication is allowed except for user 1. If selected, (1) reset password links will be replaced with links to ldap end user documentation below. (2) The reset password form will be left available at user/password for user 1; but no links to it will be provided to anonymous users. (3) Password fields in user profile form will be removed except for user 1.
So it seems this was out-of-scope at least since 7.x-2.x. However, you can probably take a look at the password reset form and without too much effort build a form that triggers a user data update if the mail token is valid.
Marking as fixed since the primary and secondary questions on password synchronization are answered. Should there remain an issue with syncing the password field to LDAP, please open a bug.
Comment #14
plingamn commentedThanks a lot grahl,
Sorry for the late response.
I have started writing custom code for password reset. Will open a new bug in case if I am stuck some where else.
I really appreciate all your help..
--
Best
Prashanth