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
711:user_groups_permissions_scim [2024/10/07 14:56] – [Participant groups] Weinlein, Thomas711:user_groups_permissions_scim [2025/01/29 16:02] (current) – [Setting the Token secret] Nerlich, Axel
Line 1: Line 1:
 ====== SCIM provisioning ====== ====== SCIM provisioning ======
  
-SCIM, or System for Cross-domain Identity Management, is an open standard for the provisioning and deprovisioning of users and user groups to enterprise applications. It is able to significantly simplify the rollout of users and their permissions in Stages.+SCIM, or System for Cross-domain Identity Management, is an open standard for the provisioning and deprovisioning of users and user groups to enterprise applications. It is able to significantly simplify the rollout of users and their permission group assignments in Stages.
  
 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.
Line 10: Line 10:
 ===== Setting the Token secret ===== ===== Setting the Token secret =====
  
-Stages generates its API tokens on the basis of a unique secret that can only be set by the Stages administrator. This should be a random string value with at least 32 two characters. This value should be stored in the file conf/secret.properties like this:+Stages generates its API tokens on the basis of a unique secret that can only be set by the Stages administrator. This should be a random string value with at least 32 characters. This value should be stored in the file conf/secret.properties like this:
  
-''apitoken.secret = <value>''+<code -> 
 +apitoken.secret = <value> 
 +</code>
  
 In the conf/config.xml file the following configuration property needs to be declared: In the conf/config.xml file the following configuration property needs to be declared:
  
-''<property name="restapi.apitoken.secret" value="${apitoken.secret}"/>''+<code -> 
 +<property name="restapi.apitoken.secret" value="${apitoken.secret}"/> 
 +</code>
  
 After that, a service restart is necessary. After that, a service restart is necessary.
 +
  
 ===== Creating an API Token ===== ===== Creating an API Token =====