Skip to content

Error codes for SCIM and legacy Okta

These are the codes CloudRepo answers with when SCIM provisioning or the move off the legacy Okta integration refuses a request. A code is the value of the error field in the response. The sign-in code is the last part of the sign-in page’s address instead.

What the API answers (status 403), and the portal shows as it is, when you add a user with a password in an organization whose identity provider provisions its members:

Your identity provider manages this organization's members. Assign this person to CloudRepo in your identity provider first.

Why: your organization has SCIM provisioning turned on, and your identity provider has not provisioned this email address. CloudRepo creates no password member for an address that the identity provider has not provisioned. Nothing is created.

Fix: assign the person to CloudRepo in your identity provider. When it has provisioned the address, add the member again.

What the API answers (status 409), when you move an organization off the legacy Okta integration with Move to modern SSO:

This organization is too large to move in one step. Contact support.

Why: the move runs in one step, and your organization holds more than one step can move. Nothing was moved.

Fix: contact support@cloudrepo.io from the owner’s address.

What the API answers (status 409), when you click Deactivate previous members on the SCIM Provisioning page:

This organization's SCIM runs through the legacy Okta integration. Contact support to remove its previous members.

Why: your organization is on CloudRepo’s legacy Okta integration, and this button works only for an organization that is not. Nothing was changed.

Fix: contact support to remove the previous members, as the message says.

What you see, on SSO Settings, when you configure, turn on or enforce single sign-on:

Your organization is still on legacy Okta, so modern SSO is refused. Move it first with Move to modern SSO on the SCIM Provisioning page.

Why: your organization still uses the legacy Okta integration, where Okta sets each member’s CloudRepo password through SCIM. Single sign-on cannot be set up, turned on or enforced for an organization on that integration.

Fix: the owner moves the organization first, with Move to modern SSO on the SCIM Provisioning page, then sets up single sign-on. Move from legacy Okta to Okta SSO and SCIM has every step, in an order that keeps your builds running.

What you see, on the SCIM Provisioning page after you confirm Move to modern SSO:

Your organization changed after you reviewed the plan, so nothing was moved.

Why: something in your organization changed after you read the plan, in Okta or in CloudRepo, so the plan you confirmed is not the one CloudRepo would carry out. Nothing was moved.

Fix: read the plan again, then move and confirm your identity again.

What the API answers (status 409), when you turn SCIM off for an organization on the legacy Okta integration:

This organization's SCIM runs through the legacy Okta integration, which cannot be turned back on once it is off, so SCIM stays on. To cut off the key your identity provider holds, rotate the SCIM key.

Why: the legacy Okta integration cannot be turned on again once it is off, so CloudRepo keeps SCIM on for an organization that still uses it.

Fix: to stop the key Okta holds, use Rotate SCIM Key on the SCIM Provisioning page. To turn SCIM off, move the organization off the legacy integration first (Move from legacy Okta to Okta SSO and SCIM); after the move, the SCIM Provisioning page offers Turn SCIM off.

What you see, when you link an address on the SSO Settings page and your organization has SCIM provisioning turned on (the API answers status 409):

you@example.com has no CloudRepo account yet. Your identity provider adds it when it provisions this person.

Why: the address you tried to link holds no CloudRepo account. With SCIM provisioning, an account exists once your identity provider has provisioned the person. Nothing is linked, and the confirmation you gave is not used up.

Fix: have your identity provider provision this person. When it has, link the address again.

What you see, on the SCIM Provisioning page when you open or confirm Move to modern SSO:

Your organization is no longer on legacy Okta, so there is nothing to move.

Why: your organization has already moved off the legacy Okta integration, perhaps from another tab.

Fix: reload the page. A card headed SCIM Endpoint means the move happened.

What the API answers (status 409), when you click Regenerate Token on the SCIM Provisioning page to turn SCIM on again:

SCIM can't be turned back on yet: members from your previous SCIM connection are still active, and a new connection could reuse their accounts for new people. Deactivate them first (Security → SCIM Provisioning: press Regenerate Token, then Deactivate previous members), then turn SCIM on again.

The response also carries count, the number of members still active, and members, up to 20 of them.

Why: you turned SCIM off, and some members of the previous connection are still active. A new connection would reuse their accounts for new people, so CloudRepo makes no token until they are deactivated. No token was made.

Fix: on the SCIM Provisioning page, use Deactivate previous members in the card headed Members from your previous SCIM connection, then click Regenerate Token again. The steps are in Switch to a different identity provider.

What you see, on the SCIM Provisioning page after you confirm Move to modern SSO:

Okta changed a member while the move was being prepared

Why: Okta sent a change to one of your members while CloudRepo was preparing the move, so your members did not move, and the organization is still on legacy Okta. Old accounts the plan named may already have ended.

Fix: open the plan again, read it, and move again.

What the API answers (status 409), when you click Regenerate Token on the SCIM Provisioning page:

SCIM settings changed while the token was being generated, so no token was made. Reload the page and try again.

Why: your organization’s SCIM settings changed while CloudRepo was generating the token, perhaps from another tab. No token was made, and the token your identity provider holds is unchanged.

Fix: reload the page, then click Regenerate Token again.

What the API answers (status 409), when you click Regenerate Token on the SCIM Provisioning page soon after turning SCIM off:

SCIM was turned off less than 5 minutes ago. Try turning it on again in a few minutes.

The response carries Retry-After, the number of seconds left.

Why: CloudRepo waits 5 minutes after SCIM is turned off before it makes a new token, so that every member of the previous connection shows in its count. No token was made.

Fix: wait for the seconds Retry-After gives, then click Regenerate Token again.

What the API answers (status 409), when you click Deactivate previous members on the SCIM Provisioning page:

SCIM is on, so its members belong to your identity provider. Deactivate them there.

If SCIM was turned on while the deactivation was running, the sentence is SCIM was turned on while previous members were being removed, so this stopped after N member(s). Any member left now belongs to your identity provider: deactivate them there. The response also carries ended and pending.

Why: SCIM is on, so the members of the organization belong to your identity provider. CloudRepo does not deactivate them from here. In the second case, it ended the first N previous members and stopped when SCIM came on.

Fix: deactivate the member in your identity provider.

What the API answers (status 409), when a SCIM token is requested for an organization whose single sign-on is not on.

Why: SCIM provisioning needs single sign-on. Until it is on, CloudRepo makes no SCIM token. The SCIM Provisioning page shows SCIM Requires SSO instead of the token controls.

Fix: turn on single sign-on first (Turn on SSO, then enforce it), then generate the token as Connect SCIM provisioning shows.

What the API answers (status 409), when you click Deactivate previous members on the SCIM Provisioning page:

Another change to your organization was saving at the same time, so this stopped after ending N previous member(s). Run this again to finish.

The response also carries ended and pending, the counts.

Why: another change to your organization was saving at the same moment, so CloudRepo stopped after the members it had already ended. The member it stopped at was not changed.

Fix: click Deactivate previous members again. It finishes the members that are left.

What the API answers (status 500), when you click Deactivate previous members on the SCIM Provisioning page:

Ended N previous member(s); M did not finish. Run this again to finish them.

The response also carries ended and pending, the counts.

Why: CloudRepo ended N previous members, and M more did not finish ending. The ones it ended stay ended.

Fix: click Deactivate previous members again. It finishes the members that are left.

What you see, on the SCIM Provisioning page after you confirm Move to modern SSO:

The move stopped before it finished

Why: the move stopped part way. Your organization is still on legacy Okta, and old accounts the plan named may already have ended.

Fix: move again.

What you see, on the SCIM Provisioning page when you turn SCIM off:

SCIM is still on. We could not check how SCIM is set up for your organization, so nothing was changed. Try again in a moment.

Why: CloudRepo could not read your organization’s settings to check whether it uses the legacy Okta integration, so it kept SCIM on and changed nothing.

Fix: try again in a moment.

What the API answers (status 503), when you click Deactivate previous members on the SCIM Provisioning page. The response carries Retry-After: 5.

Why: CloudRepo is already running as many member deactivations as it allows at once. It changed nothing in your organization.

Fix: wait a few seconds, then click Deactivate previous members again.

What you see, on the SCIM Provisioning page when you open or confirm Move to modern SSO:

CloudRepo could not read your organization’s settings, so nothing was moved. Try again in a moment.

On SSO Settings, the request fails with the page’s general message. The API answers status 503 with a Retry-After header and no message.

Why: CloudRepo could not read your organization’s settings to check whether it still uses the legacy Okta integration, so it refused the request before changing your organization.

Fix: try again in a moment.

This code comes back on the CloudRepo sign-in page’s address after a sign-in through your identity provider, as ?error= and the code.

What you see, on the CloudRepo sign-in page when you have just signed in through your identity provider:

Your organization still signs members in through the legacy Okta integration, so single sign-on was refused. Until its owner moves it to modern SSO, members sign in with the CloudRepo password Okta set for them, if it set one.

Why: your organization still uses the legacy Okta integration, so CloudRepo does not sign anyone in to it through single sign-on.

Fix: sign in with the CloudRepo password Okta set for you, if it set one. To use single sign-on, the owner first moves the organization with Move to modern SSO on the SCIM Provisioning page (Move from legacy Okta to Okta SSO and SCIM).

View as Markdown