Skip to main content

SCIM provisioning

With SCIM provisioning, your identity provider (IdP) — Okta, Microsoft Entra ID or any SCIM 2.0 client — creates, updates and removes your organization's members and groups in Jaah. You manage people in one place; Jaah follows.

Set up single sign-on first: SSO decides how members sign in, SCIM who they are.

You need:

  • A plan that includes SCIM. Without it, Features has no SCIM card. To get one, see Subscription.
  • The Org Owner or Org Admin role. The card is hidden from everyone else.

Get the base URL and a token​

  1. In the sidebar select Settings, then Features, then the SCIM card. See Your organization.
  2. Under SCIM base URL, select Copy URL. It is your console's address followed by /api/public/scim/v2.
  3. Select Generate token. A banner shows the token with Copy it now. You won’t see it again. Select Copy token, then Done. Jaah keeps only a hash of it.

Until you generate one, the list reads No tokens yet. Each token in it shows its start, whether it is Active, Stopped or Revoked, when it was last used (or Never used), and when and by whom it was created.

Whom a token acts as​

A token acts as the admin who generated it: every change it makes is recorded under their name in Audit. It stops working when that admin is disabled, deleted or no longer an Org Owner or Org Admin, and its row reads Stopped, with a line naming who is no longer an admin. Have another admin generate a new token and update your IdP.

Revoke a token​

In its row's ⋯, select Revoke, then Revoke again to confirm. Jaah refuses every later call made with it. To clear a revoked token from the list, select Remove in its row's ⋯ and confirm.

Set up Okta​

  1. In the Okta Admin Console, open your app integration for Jaah, or create one: a SAML or SWA app with SCIM provisioning, or SCIM 2.0 Test App (Header Auth) from the catalog.

  2. On the General tab, set Provisioning to SCIM and save.

  3. On the Provisioning tab, under Integration, select Edit and set:

    FieldValue
    SCIM connector base URLThe SCIM base URL
    Unique identifier field for usersuserName (the email)
    Supported provisioning actionsPush New Users, Push Profile Updates, Push Groups
    Authentication ModeHTTP Header, with the token as the Bearer value
  4. Select Test Connector Configuration, then Save.

  5. Under To App, select Edit and enable Create Users, Update User Attributes and Deactivate Users. Save.

  6. Assign people to the app. To send groups, add them on Push Groups.

Set up Microsoft Entra ID​

  1. In the Microsoft Entra admin center, open Enterprise applications, select New application, then Create your own application. Choose the non-gallery option and create it.
  2. Open Provisioning and set Provisioning Mode to Automatic.
  3. Under Admin Credentials, set Tenant URL to the SCIM base URL and Secret Token to the token. Select Test Connection, then Save.
  4. Under Mappings, open the user mapping and map userName from userPrincipalName (or mail, if that is the address people sign in to Jaah with).
  5. Set the scope — usually only assigned users and groups — and assign them under Users and groups.
  6. Start provisioning.

Entra syncs about every 40 minutes, so a change can take that long to reach Jaah.

What each change does in Jaah​

From the IdPIn Jaah
Create a userA member of your organization, with no invitation email; they sign in with that email. A person who already has a Jaah account in another organization gets an invitation instead and joins once they accept it.
Update a userTheir name, email and active state change.
Deactivate a userThe member is disabled and every live session they have ends at once. The IdP still sees them.
Reactivate a userThe member is enabled again.
Delete a userThe member is removed from your organization.
Push a groupA group with those members, described as Managed by your identity provider. Group names need to be unique within your organization only.

The Everyone group is never changed over SCIM.

Edit managed people in your IdP​

Members your IdP manages (those it sent an externalId for, as Okta and Entra ID do) and groups it created show a SCIM mark on People and Groups. Change them in your IdP: the next sync overwrites edits made in the console.

Not supported​

Bulk requests, sorting, password changes and entity tags. IdPs work without them.