Open headincl0ud opened 1 year ago
Routing to @getsentry/ecosystem for triage. ⏲️
Routing to @getsentry/enterprise for triage. ⏲️
@headincl0ud Can you email support@sentry.io with a link to this GitHub issue and include your organization slug or user email? With that information, I can unblock the bad state on your user account.
We're looking into improving the UX of our login flow, so this is valuable feedback.
@headincl0ud Can you email support@sentry.io with a link to this GitHub issue and include your organization slug or user email? With that information, I can unblock the bad state on your user account.
We're looking into improving the UX of our login flow, so this is valuable feedback.
@leedongwei done!
I think there's 2 possible solutions for this scenario:
Require SSO
is turned on for the entire organization. This would let folks identify bad configs before they are saved, and/or rescue themselves from a bad config without waiting for Sentry support to unblock them. The team is planning to improve our auth experience next year, we'll put this on the list of user pain-points to address.
Environment
SaaS (https://sentry.io/)
Version
Latest
Steps to Reproduce
Expected Result
The user should be able to access the root account and be able to remove the impacted organization from its own account.
Actual Result
After successful login with credentials (user/password) Sentry.io is redirecting to
auth/login/XYZ/?next=%2Forganizations%2FXYZ%2Fissues%2F
.It is a misconfiguration and egg-chicken issue. After removing the SSO configuration in AWS / GCP, you cannot log in to your account because of redirection. The same issue can happen in the case of changing employers. After leaving typically you can't access your corporate email, which results in blocked access to the root account.
NOTE: It is my own organization created and destroyed during Terraform destroy process. I can't access the account, I can't use the previous configuration/state.