Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
712:user_groups_permissions_scim [2025/10/16 13:17] – [SCIM provisioning] Suess, Bernhard712:user_groups_permissions_scim [2025/10/16 13:19] (current) – [SCIM provisioning] Suess, Bernhard
Line 5: Line 5:
 Stages V7.11 implements the SCIM standard version 2.0 (see [[https://scim.cloud]]), which is supported by most modern identity providers like Okta Lifecycle Management or Microsoft Entra ID. They provide the capability to configure the connection to the Stages application. Stages V7.11 implements the SCIM standard version 2.0 (see [[https://scim.cloud]]), which is supported by most modern identity providers like Okta Lifecycle Management or Microsoft Entra ID. They provide the capability to configure the connection to the Stages application.
  
-Before connecting with Stages, an API token has to be created. This will then be used by the identity provider (SAML) 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. 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.
 +
 +We recommend using SAML as authentication method together with SCIM as User and Groups modifier.