Periodic orphaned accounts update mechanism does not seem to detect orphaned users

Do you have the Field: PUID Attribute configured under Drupal Mapping, admin/config/people/ldap/user_drupal.

The permanent unique Id field has to be set for Orphan processing to work. The DN is not reliable as people change their name. If you are using Active Directory, you probably want the PUID mapped to objectsid

I think this should be added to the documentation.

Sorry I forgot to follow up on this. We no longer maintain the website where we were running into this issue, but as far as I can remember, we used UID, not PUID. If this requirement could be added to the documentation, that would be great!

Lets add a check for the PUID for the status report and display a similar warning on admin/config/people/ldap/user_drupal and admin/config/people/ldap/user

The following warning is shown when orphan processing is enabled, and the server does not have PUID.

"Periodic orphaned accounts update mechanism requires the "Persistent and Unique User ID Attribute" to be set on the LDAP server configuration. Currently, it is not set on the server test."

Automatically closed - issue fixed for 2 weeks with no activity.