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]]
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 to be 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. Additionally, before users sign in with the new Okta SSO, update their existing Sentry accounts to reflect the new email address. This can be done by changing the primary email address to the new one or adding the new email address as a secondary email. This ensures proper linking and prevents duplicate accounts.
If the above does not resolve, try the following:
Rerun the tasks from the menu in Okta to see if the alert clears.
Confirm that the sentryOrgRole set in the Okta user is all lowercase.
Ensure that there are no existing email addresses already in Sentry as an account, as we don't allow a new user to be provisioned with the same email.
Please check that you've followed all of the setup instructions outlined in our Okta SCIM Provisioning documentation here. Please also check the Troubleshooting section of this document.
Note: Bulk merges are not supported, so it’s best to address account linking proactively before rolling out SCIM/SSO widely.