LDAP: Allow mapping of user active state

[!TIP]

Help move this idea forward

• Use the 👍 reaction to show support for this feature.
• Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
• Subscribe to receive notifications about status changes and new comments.

Is your feature request related to a problem? Please describe.

We have an LDAP server providing users, which might get deactivated for certain times. With the current implementation we cannot determine whether a user is only temporarily disabled or removed from the LDAP server as to disable a user via LDAP it has to be "removed" for Nextcloud (e.g. through filters).

However, then we cannot automatically delete users, which are really deleted from LDAP.

Describe the solution you'd like

Map an active attribute from LDAP to Nextcloud.

Describe alternatives you've considered

We considered not using LDAP alltogether, e.g. using the API directly for user provisioning. However, this seems a bit overkill as it really is only a small feature missing.

Start at Nextcloud Server’s LDAP user synchronization and provisioning entry points, then trace how filtered or missing LDAP users are currently handled. Define how the mapped active attribute distinguishes temporary deactivation from removal, and add coverage for both states so the existing deletion behavior remains verifiable.