Trying to login and its forcing SSO which the account doesn't have

[Phil Dawson]

We have an account that is username/password based but its now being caught in the domains SSO policy in bitbucket whilst previously it would be username/password.

Tried the recovery link but its also now catching it.

I need Atlassian to disable SSO for that user.

[Arkadiusz Wroblewski]

Hi @Phil Dawson 

This happens likely because the account's domain is managed by an Atlassian organization enforcing SSO, which overrides standard password resets.

An Org Admin can fix this at admin.atlassian.com (Directory > Managed Accounts) by either updating the account in your IdP or moving it to a non-SSO policy. If this is a service account, API tokens or SSH keys are usually a cleaner long-term fit anyway.

If your admins are completely locked out, contact Atlassian Guard Support directly to get it sorted.

Best,

Arek 🤠

[Phil Dawson]

Hi @Arkadiusz Wroblewski it was a legacy standalone account that was username/password and had changed its email to the same as the company (from the accuired company).

We've used SSO for ages within the company, but still used the username/password login method for that account.

However trying to login today it now gets caught in the SSO and redirects. There's no option to skip SSO and enter the username/password like it did before.

There's no user within the company for this email its a joint inbox which is why the SSO then fails, and we're effectively now locked out.

[Arkadiusz Wroblewski]

So Support.

support.atlassian.com  or https://www.atlassian.com/company/contact/purchasing-licensing#/