Issue Summary

When you authenticate with Google, Log in with Google enabled will be displayed on your profile. 

If SSO is later enforced on your account (with a different IDP), this message will still be displayed, even though the user won't be able to log in with Google anymore.

Steps to Reproduce

 You'll need to have an SSO integration with an IDP (other than Google) to test this.

1. Create a managed account (an account from your verified domain).
2. Make sure that SSO is not enforced on this account.
3. Use the Continue with Google option to authenticate with this account on Atlassian.
4. Access https://id.atlassian.com/manage-profile/email
5. Note that Log in with Google will be displayed.
6. Log out of this test account.
7. Now, enforce the SSO authentication on this account.
8. Log in to the test account again, now with SSO.
9. Access https://id.atlassian.com/manage-profile/email

Expected Results

Only Log in with SAML enabled should be displayed, since the account is enforced to authenticate with SAML (through the IDP).

Actual Results

Both messages are displayed:

• Log in with Google enabled
• Log in with SAML enabled

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available