These instructions outline the necessary steps to switch from a previous SSO setup with JIT group synchronization to SCIM user provisioning. With the switch to SCIM group membership is managed in your identity provider. Depending on your identity provider and its settings, removing a user’s access or deleting them can disable or delete the DeepL account. For more information about group management, see this article.
Identity provider-specific steps can be found in the SCIM setup article for your identity provider:
If you use Entra ID with OpenID Connect, first check whether your application is an enterprise application. For more information on how to check and steps to switch, see this article.
Before you start, check and plan for the following:
- The roles and group names from your identity provider become the group names in DeepL. Check their names first.
- SCIM provisions every user in those groups. Ensure that only lusers who should be licensed are in these groups.
- Plan the switch for a time of low activity.
Prerequisites
- Admin access to DeepL and your identity provider
- Single sign-on with JIT group synchronization and groups were previously setup
- Protocol: SAML or OpenID Connect
Backup your JIT group user assignments
If you are currently using Just-In-Time (JIT) group provisioning, we suggest backing up your group assignments before starting the configuration. These assignments were made during the JIT group synchronization setup.
- Go to the Users tab of your DeepL admin account
- Click Export all users
A list of all users and their current group assignments is exported
Create the SCIM connection in your identity provider
Create the SCIM connection as described in the article for your identity provider without starting provisioning.
Delete JIT groups and disable JIT group synchronization
When you begin the SCIM provisioning process and a JIT group in DeepL has the same name as a group that was provisioned via SCIM, the SCIM-provisioned group will overwrite the JIT group. This is the intended behavior, which allows you to manage the group from your Identity Provider (IdP).
However, if a JIT group is not in scope for SCIM provisioning, meaning it will not be provisioned to the DeepL, e.g., not assigned to the application or not pushed in Okta, that JIT group will not be overwritten. It will persist in your DeepL admin account even though it is no longer managed by your IdP. This can cause confusion when managing group assignments.
Therefore, to ensure that all your groups are managed solely by SCIM, we recommend deleting all previously created JIT groups.
As you delete JIT groups, your users may temporarily lose access to DeepL. Since they are being removed from groups associated with specific subscriptions or products, they will temporarily only belong to the default group. While their current SSO session may remain valid, they will only have access to products and subscriptions linked to the default group. Keep the subscription linked to the default group, you unlink it later, see Roll out to all users.
To minimize the impact on users, we recommend the following:
- Set your DeepL default group to a basic subscription to grant users continued access to core products during this brief configuration period.
- Notify your users in advance that they may experience a temporary loss of access while you perform maintenance on the application setup.
To delete groups, follow these instructions:
- Go to Groups in your DeepL admin account
- Click the
menu next to the group you want to delete
- Select Delete group
To disable the JIT group synchronization, follow these instructions:
- Go to Settings in your DeepL admin account
- In section Team and Single sign-on click Edit next to the SSO configuration
- Uncheck JIT Group Sync, to disable JIT group synchronization
Enable SCIM in your DeepL account
- Go to the Settings of your DeepL account
- In the Team and User provisioning configuration section, click Manage user provisioning
-
Select Enable SCIM provisioning.
An SCIM admin API key will be created. You will need this API key for your OneLogin configuration.If you've previously set up JIT group synchronization, make sure to disable it to avoid any user provisioning issues. Before disabling JIT group synchronization, export your existing groups and users. - Go to your OneLogin SCIM application
- Go to the Configuration page
- In the SCIM Bearer Token field, enter your SCIM API key. You will find your SCIM API key in your DeepL admin account under Admin keys. For more information, see this article
- Click Save
Connect your identity provider and test
- Enter the SCIM API key
- Start provisioning for a few test users
- Check that each user appears only once in the correct group and can sign in with SSO
Users who already existed through JIT are matched by their email addresses. Therefore, theuserNamemust equal the SSO email value, as described in the article for your identity provider.
Roll out to all users
- Assign all users and groups
- Link a subscription to each group
- Once everyone is licensed via a group, unlink the subscription from the default group. Otherwise, every SSO user will consume a license via the default group.
Clean up
Users not assigned to the DeepL app in your identity provider and groups without access will not be deleted by SCIM. Delete them manually if you no longer need them.