How provisioning works in DataCamp
With SCIM provisioning, we allow you to automate user management on DataCamp. At the moment, the following operations are supported:
Create new users
Update a user’s metadata (first/last name, e-mail)
Remove a user from your organization
We currently do not support group management nor any other custom attributes.
Prerequisites
A DataCamp organization with an active enterprise subscription.
DataCamp organization admin access. You need to be an admin of the DataCamp organization to enable SCIM and copy its credentials.
Single sign-on (SSO) enabled and required. SCIM can only be enabled once SSO is enabled for the organization and Require SSO is turned on, because members created through SCIM have no DataCamp password and thus sign in through SSO. SCIM is added to the Okta app integration you already use for DataCamp SSO, which must be a SAML integration created with the Classic experience (formerly called the App Integration Wizard). Okta doesn't offer SCIM on other integration types.
Okta admin access. You need the Super Administrator or Application Administrator role in Okta to configure provisioning on the app integration.
User email addresses in Okta. DataCamp identifies each user by the SCIM userName attribute, which must be a valid email address. Decide which Okta attribute holds your users' email addresses, and make sure it matches the primary email address provided to DataCamp via SSO:
When the nameid format is e-mail: the nameid
When unspecified nameids are in use: the e-mail attribute
Set up
Step 1: Enable SCIM in DataCamp
Sign in to DataCamp and open your organization's Settings.
Open the SCIM tab, next to the SSO tab. If SSO is not yet enabled and required, the tab shows a banner linking to the SSO tab; complete that first.
Select Enable SCIM.
Leave the authentication method set to OAuth 2.0 (recommended). The tab now shows four values, each with a Copy button: SCIM base URL, Token endpoint, Client ID and Client secret.
Keep this tab open. We’ll need the values in a later step.
Step 2: Turn on SCIM in your Okta app integration
Sign in to the Okta Admin Console.
Go to Applications > Applications and open the SAML app integration you use for DataCamp SSO.
On the General tab, select Edit in the App Settings section, set Provisioning to SCIM, and select Save. A Provisioning tab appears.
The SCIM option is only available on SAML integrations created with the Classic experience (formerly called the App Integration Wizard). If your integration was created that way and the option still doesn't appear, contact Okta Support to check that provisioning is enabled for your Okta org. If you did not create the integration that way, you will have to recreate an app and set up SSO again.
Step 3: Connect Okta to DataCamp
Open the Provisioning tab. Under Settings > Integration, select Edit.
In SCIM connector base URL, paste the SCIM base URL from the DataCamp SCIM tab.
In Unique identifier field for users, enter userName.
Under Supported provisioning actions, select Push New Users and Push Profile Updates. Leave the import and group options cleared for now (Step 6 explains when to turn on import).
Set Authentication Mode to OAuth 2 and Grant Type to Client Credentials.
Copy each remaining value from the DataCamp SCIM tab into the matching Okta field:
Okta field | Value to copy from the DataCamp SCIM tab |
Access token endpoint URI | Token endpoint |
Client ID | Client ID |
Client Secret | Client secret |
Select Test Connector Configuration. Okta confirms that it can reach DataCamp with these credentials.
Select Save.
Step 4: Configure provisioning to DataCamp
On the Provisioning tab, under Settings > To App, select Edit.
Enable Create Users, Update User Attributes and Deactivate Users. Leave Sync Password turned off, as members sign in through SSO.
Select Save.
Review the attribute mappings further down the same page. DataCamp supports the following attributes:
Username (required): used at DataCamp to identify users. Should be a valid e-mail address. Okta sends the application username, set under Sign On > Credentials Details > Application username format. Set it to the same value as the e-mail address provided via SSO (either as nameid or as a SAML attribute)
name.givenName (optional)
name.familyName (optional)
Step 5: Link users who were assigned before SCIM was turned on
Skip this step if nobody was assigned to the app before you turned on SCIM. Okta can only update or remove a user in DataCamp once it has linked that user to their DataCamp account. Users who were already assigned to the app when you turned on SCIM are not linked, so when you unassign or deactivate them, Okta sends nothing to DataCamp and they stay in your DataCamp organization. Importing users from DataCamp creates the link.
On the Provisioning tab, under Settings > Integration, select Edit. Under Supported provisioning actions, select Import New Users and Profile Updates, then select Save. A To Okta page appears under Settings, and an Import tab appears.
Under Settings > To Okta, select Edit in the User Creation & Matching section. For Imported user is an exact match to Okta user if, choose the option that compares the email address you used as the application username in Step 4, for example Email matches. Leave Auto-confirm exact matches and Auto-activate cleared so you can review the matches, then select Save.
On the same page, leave Profile & Lifecycle Sourcing turned off, so Okta remains the source of your users' profiles.
Open the Import tab and select Import Now. Okta reads the members of your DataCamp organization and lists each one with the Okta user it matches.
Select the users shown as exact matches and select Confirm Assignments. Don't confirm users that have no match: confirming them creates new users in Okta and assigns them to the app.
Confirmed users are now linked. From now on, unassigning or deactivating one of them in Okta removes them from your DataCamp organization.
FAQ
Can I add a user to my organization who already has a personal account with his work e-mail?
Not via SCIM - an error will be shown in the logs explaining that the user already has a personal account. To add this user, you will have to manually invite them from the DataCamp platform.
If I remove a user from my organization, will their account be deleted?
No, the account will be removed from your organization, but will still be available in the DataCamp platform. If the user wants to access their account later, they can reach out to DataCamp support, who can recover the user’s access.