Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auth - Azure SSO SCIM: Once users enable 2FA the unchangeable state of the user account gets removed #77625

Open
Angelodaniel opened this issue Sep 17, 2024 · 3 comments
Labels
Product Area: Settings - Auth Sync: Jira Apply to auto-create a Jira shadow ticket

Comments

@Angelodaniel
Copy link
Member

Angelodaniel commented Sep 17, 2024

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  1. Enable SSO + SCIM
  2. Provision the user from SCIM
  3. User enables 2FA

This makes it possible again that the org owner or own user can remove the user account which should not be possible

Expected Result

We would like to enforce 2FA, but can't at the moment as this will likely result in some unwanted behaviour in user management. It is possible to reconnect the user to Sentry, but they will end up without any Team. A Group Sync from AzureAD/EntraID, or removing and adding a user back to the group does not seem to fix this

Actual Result

enabling 2FA removes this restriction from SCIM

Product Area

Settings - Auth

Link

No response

DSN

No response

Version

No response

┆Issue is synchronized with this Jira Improvement by Unito

@Angelodaniel Angelodaniel added the Sync: Jira Apply to auto-create a Jira shadow ticket label Sep 17, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Sep 17, 2024

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Sep 17, 2024

Routing to @getsentry/product-owners-settings-auth for triage ⏲️

@getsantry getsantry bot moved this from Waiting for: Support to Waiting for: Product Owner in GitHub Issues with 👀 3 Sep 17, 2024
@leedongwei
Copy link
Member

Thanks for the bug report. I'll try to schedule this for the rotational crew to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Product Area: Settings - Auth Sync: Jira Apply to auto-create a Jira shadow ticket
Projects
Status: No status
Development

No branches or pull requests

3 participants