getsentry / getsentry/sentry

Okta SCIM Integration Issue with Sentry

Open
#81,395 3 comments 0 reactions 0 assignees View on GitHub
Bug Product Area: Settings - Auth Sync: Jira
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

SaaS ([https://sentry.io/]())

### Steps to Reproduce

We have a user who is experiencing two persistent issues with the SCIM integration between Okta and Sentry:

Missing User Details: Users are created in Sentry with only their email address populated. First and last names remain blank, even after the user accepts the invitation and logs in.

Deactivation Issue: Unassigning a user in Okta does not deactivate or remove the user in Sentry. The account remains active.

Steps to Reproduce:
Configure SCIM integration between Okta and Sentry.
Assign a user via Okta to Sentry.
Observe missing first and last names in Sentry.
Unassign the user in Okta and note that the Sentry account remains active.

See the linked Jira ticket for the Zendesk issue

### Expected Result

SCIM should populate first and last names in Sentry during provisioning.
Unassigning a user in Okta should deactivate their Sentry account.

### Actual Result

Configuration has been reviewed and re-done using the dedicated Okta authenticator.
Profile sync and role assignment work, but names remain blank.
Deactivation through Okta has no effect on Sentry accounts.

### Product Area

Settings - Auth

### Link

*No response*

### DSN

*No response*

### Version

*No response*

┆Issue is synchronized with this [Jira Improvement]() by [Unito]()

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.