User Still Appearing in Sentry After Removal via Okta
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
### Environment
SaaS (https://sentry.io/)
### What are you trying to accomplish?
Remove a user from Sentry by deprovisioning them in Okta (Sentry SCIM provider integration).
### How are you getting stuck?
After removing a user in Okta, they still show up in the Sentry organization.
The user has correctly configured Okta (and the Sentry provisioner) according to our official documentation for [Okta: SSO](https://docs.sentry.io/organization/authentication/sso/okta-sso/) [Okta: SCIM](https://docs.sentry.io/organization/authentication/sso/okta-sso/okta-scim/).
[Short video provided](https://app.intercom.com/a/inbox/onh0p2wm/inbox/shared/all/conversation/215474146389595#part_id=comment-215474146389595-44728662207)
### Where in the product are you?
Settings - Members
### Link
_No response_
### DSN
https://f8b5dd0e1f11a627797914e8ab325ba5@o1335797.ingest.us.sentry.io/4509867328667650
### Version
_No response_
Contributor guide
Research direction
Start by reviewing the linked Okta SSO and SCIM documentation and the behavior in Settings - Members, then use the provided video and reproduction details to investigate deprovisioning. Done means a user removed through Okta no longer appears in the Sentry organization.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100