Skip to main content

I received Okta SCIM Provisioning Error "Error While Creating User"

Updated over a month ago

Issue

When completing the Okta SCIM Provisioning Configuration setup guide I am receiving the following error at the end when using automatic provisioning:

Automatic provisioning of user UserNameHere to app Sentry failed: Error while creating UserNameHere Error setting property, appUser:UserNameHere, property=sentryOrgRole error=[Error in object 'appUser': codes [invalidValueTypeForProperty.appUser, invalidValueTypeForProperty]; arguments [sentryOrgRole]; default message [Unsupported data type value for given key]]

Screenshot 2024-06-10 at 12.39.21 PM.png

Applies To

  • Business and Enterprise Plans

  • Okta SCIM Provisioning users

Symptoms

I'm unable to successfully complete Okta SCIM Provisioning and have all users successfully provisioned.

Resolution

If the email already exists in Sentry as an account, we don't allow a new user provisioned with that email which is usually why we see this error occur. First make sure you import all users from Sentry and link them to their Okta counterparts before assigning new ones. This is in reference to the image in our docs (also seen below); specifically referencing the "Import" tab next to "Provisioning", which should pull the already existing accounts from Sentry so you can link them in Okta.

Screenshot 2024-06-10 at 1.34.51 PM.png

If the above does not resolve try the following:

  • Rerun the tasks from the Tast menu in Okta to see if the alert clears.

  • Confirm that the sentryOrgRole you have set in Okta is the same as the default role you have set in your Auth -> Settings in Sentry, see below.

Screenshot 2024-06-10 at 3.05.25 PM.png
  • Ensure that there are no existing email addresses already in Sentry as an account as we don't allow a new user provisioned with the same email.

  • Please check that you've followed all of the setup instructions outlined on our Okta SCIM Provisioning documentation here. Please also check the Troubleshooting section of this document.

Did this answer your question?