Skip to main content

Oloid Configuration Guide for Okta SCIM Client

Learn how to setup and use user provisioning to sync users from Okta to Oloid.

Updated over 3 weeks ago

Overview

You can provision users from Okta to Oloid to reduce manually adding each employee to Oloid. The provisioning process reduces administrative errors and is a great way to save time and efforts.

With Okta to Oloid provisioning features, you can automate these tasks

  • Push new users – Any users you create into Okta can be provisioned / created into Oloid.

  • Push profile updates – Profile updates done in Okta are pushed to Oloid.

  • Push user deactivation – Deactivating or removing a user in Okta terminates the user in Oloid.

How to configure SCIM provisioning from Okta to Oloid

Prerequisite:

You must have permission to create application in Okta Console.

  1. Log in to Okta Tenant Administration console.

  2. Go to Applications > Applications and click Browse App Catalog.

  3. Search for Oloid (as shown below).

  4. Add the integration for Oloid app.

  5. Enter name as Oloid – SCIM or as per your preference in the Application label.

  6. Go to Provisioning tab and click Configure API Integration.

  7. Do the following:

    1. Select Enable API integration.

    2. Enter Base URL.

    3. Enter API Token.

    4. Click Test API Credentials.

      Validation should succeed and you should see the message "Okta-SCIM was verified successfully".

    5. Click Save.

  8. Go to Provisioning >Settings >To App.

  9. Enable the following sections:

    1. Create Users

    2. Update User Attributes

    3. Deactivate Users.

    4. Under attribute mapping, map following attributes:

      Note: Email is case insensitive attribute in Oloid.

  10. For enabling Oloid face Authentication in Okta please check How to configure OIDC - Okta IDP Profile.

The Okta SCIM client is configured.

Troubleshooting

If you have any questions or difficulties with your Oloid / Okta SCIM integration please contact Oloid Support

Related Documents:

Did this answer your question?