Skip to main content
All CollectionsTechnical ResourcesSecurity & SSO
Setting up SCIM Provisioning with Okta

Setting up SCIM Provisioning with Okta

Enable user provisioning between Okta and Hive with our SCIM 2.0 OIN integration.

A
Written by Anton Suarez
Updated over 2 weeks ago

Requirements

You must have an existing Hive workspace with the Enterprise Security Add-on. You must also be a system-level administrator in that Hive workspace.

Configuration Steps

After adding Hive SCIM from the Okta OIN you will need to fill out a value for the ‘Workspace Identifier’ field. This is your workspace id, that you can see in Hive by going to the top-right user menu (click on your Avatar) and then choose the 'Edit profile' option. From there go to the 'API Info' link on your left menu. You will see your workspace id there (and other fields we will use later in the setup as well so keep this page open). Copy this workspace id into the 'Workspace Identifier' field in the Okta integration setup and click “Done”.

Next you need to click “Configure API Integration” on the Hive SCIM Provisioning tab.

The ‘API Token’ field needs to be filled in with the ‘API Key’ value you have visible on the Hive API Info page where you also copied your workspace id from.

Once entered in, test those credentials with “Test API Credentials” to validate that you can properly authenticate with the Hive SCIM API. Click ‘Save’ when done.

There should now be a Provisioning tab visible in your Okta application setup. Click on the ‘To App’ setting option. You can select any of the following options:

  • Create Users (leave 'Set password when creating new users' unchecked)

  • Update User Attributes

  • Deactivate Users

Click ‘Save’ when done. Please note that we do not support syncing passwords, or setting them on your user in Hive through this integration.

Attributes and Mapping

We currently support only the following field mappings for users:

  • User ID: (userName [must be an email])

  • First Name: (name.givenName)

  • Last Name: (name.familyName)

  • Email: (emails [in our system this will be the same as what was passed in as userName])

Any other field mappings from Okta to Hive will just be ignored and not persisted within Hive.

Did this answer your question?