SenseCrypt Docs
Integrations

Okta SCIM provisioning

Provision users and groups from Okta into a SenseCrypt tenant with the SenseCrypt app in the Okta Integration Network: features, setup, attribute mapping and troubleshooting.

This guide sets up the SenseCrypt app in Okta so Okta provisions users and groups into your SenseCrypt tenant over SCIM 2.0. Okta stays the source of truth: people you assign in Okta are created in SenseCrypt, profile changes follow them, and unassigning them suspends them.

For the SCIM API itself (filters, errors, the enterprise extension), see SCIM provisioning.

Supported features

  • Create users. A user assigned to the app in Okta is created in SenseCrypt.
  • Update user attributes. Profile changes in Okta are sent to SenseCrypt. Okta sends them as a full replace (PUT).
  • Deactivate users. Unassigning a user, or deactivating them in Okta, sets them inactive in SenseCrypt. That suspends the user at once and revokes their device keys, passkeys, refresh tokens and browser sessions.
  • Push groups. Groups you push from Okta are created in SenseCrypt, and membership changes follow (PATCH). Okta can also rename and delete a pushed group.

Not supported:

  • Password sync and password changes. SenseCrypt is passwordless. Users sign in with their face on the SenseCrypt Authenticator app, so there is no password to send.
  • Import of a custom user schema.

Requirements

  • A SenseCrypt tenant, and an administrator who can open the SCIM Tokens page in the admin console.
  • Your tenant's host. It is the host of your tenant's issuer, <your-tenant>.sensecrypt.com, or a verified custom domain such as auth.example.com. See Multi-tenancy.
  • An Okta administrator who can add apps and configure provisioning.

Step 1: Create a SCIM token in SenseCrypt

  1. In the SenseCrypt admin console, open SCIM Tokens and click New SCIM token.
  2. Give it a label such as Okta, and an expiry if your policy needs one.
  3. Copy the token. It starts with ssct_ and is shown only once.

The token works for this tenant only, and you can revoke it from the same page at any time.

Step 2: Add the SenseCrypt app in Okta

  1. In the Okta Admin Console, go to Applications > Applications and click Browse App Catalog.
  2. Search for SenseCrypt, open it and click Add Integration.
  3. Under General settings, enter your tenant host in SenseCrypt tenant host, for example acme.sensecrypt.com. Enter the host only, without https:// or a path. Okta builds the SCIM address from it: https://<host>/v1/idp/scim/v2.
  4. Click Done.

Step 3: Turn on provisioning

  1. In the app, open the Provisioning tab and click Configure API Integration.
  2. Select Enable API integration.
  3. Paste the SCIM token from step 1 into API Token.
  4. Click Test API Credentials. Okta should report that the credentials were verified. Then click Save.
  5. Under Provisioning > To App, click Edit and turn on Create Users, Update User Attributes and Deactivate Users. Turn off Set password when creating new users, because SenseCrypt is passwordless and has no password to set. Click Save.

Step 4: Assign people and push groups

  1. On the Assignments tab, assign the users or groups who should exist in SenseCrypt.
  2. On the Push Groups tab, push the groups whose membership SenseCrypt should know about. In SenseCrypt, you can attach those groups to applications to control who may sign in to them. See Groups and access.

Attribute mapping

Okta sends these SenseCrypt attributes:

OktaSenseCrypt (SCIM)
UsernameuserName
First namename.givenName
Last namename.familyName
Primary emailemails (primary, work)
Employee number, cost center, organization, division, department (if you map them)the enterprise extension fields of the same names

userName and a primary email are required when a user is created. SenseCrypt stores the externalId Okta sends and echoes it back.

What users see

A user Okta creates exists in SenseCrypt but cannot sign in yet, because SenseCrypt has no face for them. The first time they sign in, they install the SenseCrypt Authenticator app and enrol their face. That claims the account Okta created and keeps its groups. See How SenseCrypt works.

Troubleshooting and tips

  • Test API Credentials fails with 401. The token is wrong, has been revoked, or has expired. Create a new one in step 1 and paste it again.
  • A user fails to create with a uniqueness error (409). A user with that userName or email already exists in the tenant, for example one an administrator added in the console. Remove the duplicate, or change the Okta username, and retry the task in Okta.
  • A reactivated user has to enrol again. Deactivation revokes the user's device keys and passkeys, so reactivating them in Okta restores the account but not the enrolment. They enrol their face again on next sign-in.
  • Pushed groups can't be edited in the SenseCrypt console. Groups that Okta manages are read-only there, so Okta stays authoritative. Change them in Okta.
  • Removing someone from a pushed group revokes their refresh tokens for the applications they lose, so their access ends when the current access token expires, and new sign-ins to those applications are refused. It does not suspend the user. Use deactivation for that.

Support

Contact SenseCrypt support at support@seventhsense.ai, or see Support.

On this page