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,
We're currently working on a project where we should:
- Import users from AD
- Let users login with their AD credentials/session
We import the user accounts through LDAP Feeds and it seems to work well.
About the PUID: we need to implement some logic, cause the PUID is property1
unless property2
is provided. If this is the case, then property2
is the PUID.
My question is: should I replicate that logic in LDAP User mapping (on creation, on synch)? And if yes, how can I do that?
Thanks!
Comments
Comment #1
grahlHi
So this might be too late for you but just to follow-up: You should not need to repeat that assignment during sync events. The persistent user id is an attempt to assign the correct attribute value for the correct server to a user and it should not need to be changed during operations. Once the LDAP user is loaded the sync operations should just defer to it. Granted I have not verified your case personally but this is the way I believe it should work.
If you had feedback from your project itself maybe you could share it with the community for others having similar issues?