getsentry / getsentry/sentry

Duplicate email invite when transitioning user base into SCIM managed state

Open
#72,224 2 comments 0 reactions 0 assignees View on GitHub
Bug Product Area: Sign In
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

1. Disable SCIM
2. Add member to org with user@emailA.com
3. Enable SSO
4. Enable SCIM
5. Member login with user@emailB.com

### Expected Result

I would expect that after the identity of the member account gets merged, the member should be able to login with email B via SSO

### Actual Result

A first invite gets sent to user@emailB.com when they try to log in for the first time. If the user now tries to log in with user@emailA.com before the invite sent to emailB is accepted, Sentry will send a duplicate invite and not try to merge the accounts

[Internal Customer Case](https://www.notion.so/sentry/Issues-transitioning-user-base-into-SCIM-managed-state-2d0cb3fb2f37486fa50a3540388a52bf?pvs=4)

### Product Area

Sign In

### Link

_No response_

### DSN

_No response_

### Version

_No response_

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.