Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
19
-
Minor
-
Description
Issue Summary
When an Atlassian account has SSO enforced(SAML) and the end user uses social login to log in - the user gets an error message:
Hmm... we're having trouble logging you in. Please try again with a different authentication method.
The switch from social to SAML login flow should be more seamless - or another message should be displayed for the "social_login_managed_user" condition. This is confusing for end users and plants the idea that something might be wrong with the account.
This issue doesn't affect the functionality of the account - the end user should be logged in as expected despite the error message being displayed.
Steps to Reproduce
- Enforce SSO(SAML) for an end user
- End user logs in via social login, e.g. "Continue with Microsoft"
Expected Results
id.atlassian.com doesn't display any error message or shows message explaining that the end user will be logged in via SAML due to the current configuration.
Actual Results
"Hmm... we're having trouble logging you in. Please try again with a different authentication method."
After the above screen is shown for a moment, the user is logged in as expected.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
Logging in via SAML SSO that does not use the social "Login with Microsoft" method (click blue "Continue" button instead or perform an IdP-initiated login) will not trigger this error message.
This issue doesn't affect the functionality of the account - the end user should be logged in as expected despite the error message being displayed.