Org admin locked out due to SSO misconfiguration

[Sam Seifert]

I got overconfident while attempting to configure SSO for my org. We're piloting Atlassian products for a larger rollout and I was getting SSO up and running. Basically, authentication passes on the Entra side, but Atlassian doesn't like what it sees, and errors out. I had to log in on my personal email here to attempt to get help, as it seems there's no other way to contact support about this....

Org ID: 8c2c690d-c9c5-49b5-a3e3-58c6fb0535e3

GUID on the failed login redirect: 38528e7f-63ef-4c62-0929-159321896e15

Please help! I need atlassian to disable SSO so I can get in at the least. Best case, help me configure SSO with Entra. 

Thank you very much.

[Trudy Claspill]

Hello @Sam Seifert 

Welcome to the Atlassian community.

I have flagged your post here to raise it to the attention of Atlassian Team members. They should get back to you within 2 business days.

[Sam Seifert]

Thank you very much. I guess I'll stop sitting here hitting "refresh" then. :D

[Jessica]

Hi @Sam Seifert 

Sorry to hear you got locked out of your org admin account due to the SSO.

Generally for those cases, we recommend adding an account outside the domain as another Organization admin to help, in case misconfiguration happens.

In any case, since it is not possible to disable it now, we created a ticket on your behalf and transferred it to our Atlassian Guards friends to help you with the SSO!

You should have received an email about it, but please check your requests at https://support.atlassian.com/requests, as the ticket number should have changed from the one you got in the email, as we have transferred it.

Feel free to contact us and leave a comment from there, as we will continue all validations and troubleshooting from there.

Regards,
Jessica