Okta SCIM Group push failed on 'User not found' error, but user present & verified in Sentry
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Re-provisioning user:
- Remove the existing affected user from Sentry and Okta
- Re-provision the user in Okta
- Re-provision the user to the select Okta group
- Push the Okta group
- Error:
FAILURE: Not Found / User not found
Expected Result
Once the user is defined and added to the Okta group, pushing the group should result in the user now being part of the new group, with no errors raised.
Actual Result
Okta errors out with FAILURE: Not Found / User not found error. Okta logs show "reason": "Not Found. Errors reported by remote server: User not found."
User is never provisioned to the group and the group cannot be updated, but the user will exits in their Members UI.
Product Area
Settings - Integrations
Link
No response
DSN
No response
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing the SCIM and Okta group-push handling in the Settings - Integrations area, then reproduce the provisioning sequence described in the issue. Done means an existing, verified Sentry user can be pushed into an Okta group without a User not found failure, with regression coverage for the case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100