Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
711:user_groups_permissions_scim [2025/03/25 12:45] – Nerlich, Axel | 711:user_groups_permissions_scim [2025/09/09 12:06] (current) – Nerlich, Axel | ||
---|---|---|---|
Line 6: | Line 6: | ||
Before connecting with Stages, an API token has to be created. This will then be used by the identity provider to authenticate against the Stages application. | Before connecting with Stages, an API token has to be created. This will then be used by the identity provider to authenticate against the Stages application. | ||
+ | |||
+ | To connect Stages to an identity provider via SCIM, the provider must be configured by a local system administrator. The corresponding configuration instructions can be found below. | ||
===== Setting the Token secret ===== | ===== Setting the Token secret ===== | ||
Line 63: | Line 65: | ||
The license type of a user can be set with the following SCIM core attributes for the User resource: | The license type of a user can be set with the following SCIM core attributes for the User resource: | ||
- | * '' | + | * '' |
- | * '' | + | * '' |
Possible Stages license type idents: NONE, ADMIN, ADMIN_ONLY, AUTH_PROCESS_READER, | Possible Stages license type idents: NONE, ADMIN, ADMIN_ONLY, AUTH_PROCESS_READER, | ||
- | For license types in the default license pool, the license pool name is omitted, but the double underscore separator is kept. Example value: | + | For license types in the default license pool, the license pool name is omitted, but the double underscore separator is kept. Example value: |
===== Addressing the SCIM endpoint ===== | ===== Addressing the SCIM endpoint ===== |