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 set to 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 must sign in through SSO. Provisioning is set up in a separate SP connection, so the SP connection you already use for DataCamp SSO stays as it is.
PingFederate 10.1 or later with the SCIM Provisioner add-on. DataCamp authenticates SCIM requests with OAuth 2.0 client credentials. The SCIM support built into PingFederate doesn't offer this grant type, so you need the SCIM Provisioner add-on, available from the Add-ons tab of the PingFederate downloads page or the Ping Identity Marketplace. Installing it requires access to the PingFederate server files and a restart (see Step 2).
PingFederate admin access. You need an administrator account in the PingFederate administrative console that can manage server settings and SP connections.
A user directory connected as a data store. PingFederate reads the users to provision from an LDAP data store, such as Active Directory, and needs a database for outbound provisioning to store its sync state.
User email addresses in your directory. DataCamp identifies each user by the SCIM userName attribute, which must be a valid email address. Decide which directory attribute holds your users' email addresses (for example mail), 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: Install the SCIM Provisioner and enable outbound provisioning
Skip this step if the SCIM Provisioner is already installed and outbound provisioning is already enabled on your PingFederate server.
Download the SCIM Provisioner .zip file and stop PingFederate.
Extract the archive and copy the contents of its dist folder into <pf_install>/pingfederate/server/default/deploy.
In <pf_install>/pingfederate/bin/run.properties, set pf.provisioner.mode to STANDALONE and save the file. If you run PingFederate in a cluster with provisioning failover, use FAILOVER as described in Ping's clustering guide.
Start PingFederate. In a cluster, repeat the file copy and restart on each engine node.
In the administrative console, go to System > Server > Protocol Settings, open the Outbound Provisioning tab, select a database in Provisioning Data Store (or create one with Manage Data Stores), and save.
Step 3: Create a provisioning connection for DataCamp
Go to Applications > Integration > SP Connections and select Create Connection.
On the Connection Template tab, select Use a template for this connection, choose SCIM Provisioner in the Connection Template list, and select Next. If the template is not listed, the add-on is not installed yet; go back to Step 2.
On the Connection Type tab, make sure Outbound Provisioning is selected, and select Next.
On the General Info tab, enter a Connection Name such as DataCamp SCIM, and select Next.
Step 4: Connect PingFederate to DataCamp
On the Outbound Provisioning tab, select Configure Provisioning. The Target page opens.
Set SCIM Version to 2.0 and Authentication Methods to OAuth 2 Client Credentials.
Copy each value from the DataCamp SCIM tab into the matching PingFederate field:
PingFederate field | Value to copy from the DataCamp SCIM tab |
SCIM URL | SCIM base URL |
Token Request Endpoint | Token endpoint |
Client ID | Client ID |
Client Secret | Client secret |
Leave Scope empty. Under SCIM Overrides, leave Unique User Identifier set to userName and leave Filter Expression empty.
Under Provisioning Options, keep User Create, User Update and User Disable / Delete selected, leave Provision Disabled Users cleared, and leave Remove User Action set to Disable.
Select Next. PingFederate checks these credentials when you activate the channel and the connection in Step 6.
Step 5: Choose which users to provision
On the Manage Channels page, select Create. On Channel Info, enter a name such as DataCamp users, and select Next.
On Source, select the LDAP data store that holds your users, and select Next. Adjust Source Settings for your directory type if needed, and select Next.
On Source Location, enter the Base DN for users and either a Group DN or a Filter that selects the people who should get a DataCamp account. Leave the groups section empty: DataCamp provisions users only. Select Next.
On Attribute Mapping, map your directory attributes to the SCIM attributes. Datacamp supports the following attributes:
userName (required): used at DataCamp to identify users. Should be a valid e-mail address. 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)
externalId (optional)
Select Next.
Step 6: Start provisioning
On the channel's Activation & Summary page, set Channel Status to Active and select Done. Select Done again on Manage Channels, then Next on Outbound Provisioning.
On the connection's Activation & Summary tab, turn on the connection with the toggle above the Summary section, and select Save.
PingFederate now provisions every user that matches the Source Location and keeps them in sync. When a user is disabled or deleted in your directory, or no longer matches the Source Location, PingFederate removes them from your DataCamp organization.
Review the results in <pf_install>/pingfederate/log/provisioner.log.
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.