Skip to content

Connect SCIM provisioning with Okta or Microsoft Entra ID

SCIM lets your identity provider add, update and remove the people in your CloudRepo organization for you. Connect Okta or Microsoft Entra ID once, and the people you assign to CloudRepo there get a CloudRepo account. When you remove someone there, their CloudRepo access ends too. SCIM is included on every plan.

Members still sign in through single sign-on (SSO). SCIM keeps the list of members in step with your identity provider.

  1. Turn on SSO for your organization, as step 9 of the SSO guide shows.

    Expected: SSO Settings shows the Enabled badge.

  2. Check that you can sign in to CloudRepo as your organization’s owner, with your second factor.

    Expected: the CloudRepo dashboard.

  3. In your identity provider, unassign your organization’s owner from the CloudRepo app. The owner is managed in CloudRepo, not by your identity provider, so CloudRepo refuses to create a user at the owner’s address, rename a user to it, or reactivate a user there.

    Expected: the owner is not among the people assigned to the app.

  1. In the sidebar, click Security, then the card headed SCIM Provisioning.

    Expected: the SCIM Provisioning page, with a card headed SCIM Endpoint. If it shows SCIM Requires SSO instead, SSO is not on yet: go back to Before you start.

  2. Under Base URL, copy the address.

    Expected: an address like https://your-org.mycloudrepo.io/scim/v2, with your organization ID in it.

  3. Click Regenerate Token.

    Expected: a dialog headed Regenerate SCIM Token.

  4. In the dialog, click Regenerate Token.

    Expected: a dialog headed Confirm Your Identity asks for your Authenticator Code.

  5. Enter the code from your authenticator app and click Confirm.

    Expected: a card headed SCIM Token Generated shows the token, with the warning This token will not be shown again.

  6. Click Copy, and keep the token for your identity provider.

    Expected: the button reads Copied!.

  7. Click Done.

    Expected: the token card closes. CloudRepo never shows this token again.

Your identity provider needs two values from CloudRepo:

  • Base URL: the address you copied in step 2, such as https://your-org.mycloudrepo.io/scim/v2.
  • The SCIM token, sent as Authorization: Bearer <token>.
  1. In Okta, add the SCIM 2.0 Test App (Header Auth) app from Okta’s app catalog, and turn on its provisioning. Set its Base URL to the base URL, and its Authorization header value to Bearer followed by a space and the token.

    Expected: Okta’s connection test passes.

  2. Turn on Create Users, Update User Attributes and Deactivate Users, then assign the app the people who use CloudRepo.

    Expected: each person you assigned is listed on the Users page in CloudRepo.

  1. In Microsoft Entra ID, create an Enterprise Application for CloudRepo, open its Provisioning page, and set Provisioning Mode to Automatic. Set Tenant URL to the base URL and Secret Token to the token.

    Expected: Entra’s Test Connection passes.

  2. Assign the app the people who use CloudRepo, and start provisioning.

    Expected: each person you assigned is listed on the Users page in CloudRepo.

With SCIM connected, when you remove or deactivate someone in your identity provider, they lose access to CloudRepo when your identity provider sends the change, and their password and their tokens stop working. Subscriber keys they created, and your organization’s service keys, keep working.

This holds for removals you make after SCIM is connected. Anyone you removed in your identity provider before you connected SCIM may still have a CloudRepo account: remove them on the Users page yourself.

  1. On the SCIM Provisioning page, click Regenerate Token, and follow Turn SCIM on from step 4.

    Expected: a card headed SCIM Token Generated shows the new token.

  2. In your identity provider, replace the SCIM token with the new one.

    Expected: your identity provider’s connection test passes with the new token. The old token no longer works.

To move SCIM to a different identity provider, turn SCIM off and then on again. Regenerating the token alone keeps your previous connection’s members.

  1. On the SCIM Provisioning page, click Turn SCIM off. In the dialog, click Turn SCIM off, then enter the code from your authenticator app and click Confirm.

    Expected: a card headed SCIM is off. If CloudRepo refuses because your identity provider has not finished removing a member, finish that removal there, then try again.

  2. Click Regenerate Token.

    Expected: a dialog headed Regenerate SCIM Token, or a card headed Members from your previous SCIM connection.

  3. If you see that card, click Deactivate previous members, read the list, and click Deactivate previous members in the dialog. Then enter the code from your authenticator app and click Confirm.

    Expected: the card says how many previous members were deactivated, and that you can regenerate the SCIM token now. Their access has ended. Your new identity provider adds back anyone it assigns.

  4. Click Regenerate Token, follow Turn SCIM on from step 4, and connect your new identity provider as above.

    Expected: each person the new identity provider assigns is listed on the Users page.

If the SCIM Provisioning page shows a card headed Legacy Okta SCIM, your organization is on CloudRepo’s legacy Okta integration, and this section does not apply. That integration has no Turn SCIM off: move your organization first, with Move from legacy Okta to Okta SSO and SCIM.

The codes CloudRepo answers with while you connect SCIM, and how to fix each, are on Error codes for SCIM and legacy Okta.

View as Markdown