User Management
In this section you can add a LDAP or SAML authentication, configure a OAuth service or define what should happen when deleting a user.
Last updated
In this section you can add a LDAP or SAML authentication, configure a OAuth service or define what should happen when deleting a user.
Last updated
Define what should happen, when someone deletes a user in the user management.
Ask
When someone clicks on the minus to delete a user, they'll be asked if the user should be archived or deleted.
Archive
When someone clicks on the minus to delete a user, the user will be archived. Archived users can't access the system but can be un-archived by administrators.
Delete
When someone clicks on the minus to delete a user, the user will be deleted. Deleted users can't access the system.
Please note, that in both cases "Archive" and "Delete", the collections of the users will be deleted and cannot be restored.
Enable all event types that should store the user. Otherwise the event will not be connected to a user.
Define which data of the user should be copied to the events. This is independent from the event user. If the user get's deleted or pseudonymized, this data remains in the events.
Add pairs of Client IDs and Secrets for the OAuth2 Authentication.
Name: Name of the Client (used as Client ID)
Secret: Client Secret, must be entered as a Bcrypt Hash
Redirect URIs: List of callback URLs to the local client, needed for some OAuth2 Authentication flows
Expiration Time: Access Token: Time after which the Access Token expires and needs to be refreshed, default: 24 hours
Expiration Time: Refresh Token: Time after which the Refresh Token expires, default: 720 hours
Select which user information should be returned over the OpenID endpoint oauth2/userinfo.
This big topic has its own page in our Tutorials.
This big topic has its own page in our Tutorials.
