Login error says to use email and password but Single Sign-On is required

[morganperre]

Hello @Sarah_Wessel,

Thanks for reaching out and for this clear and detailed topic.

Unfortunately, I’m not able to reproduce the same behavior.

@Sarah_Wessel

I think this may be because they originally used email and password login before our project switched over to requiring SSO.

It shouldn’t cause any trouble as long as they are registered in your SSO (IDP provider).

I just had a look at your SSO configuration and it turns out it is not set up for now. SSO is turn-on from the organization settings. Then you can log in to Forest Admin using the Single Sign-On as described here.

• Did you change anything in the meanwhile?

@Sarah_Wessel

Expected behavior

When we switched the project to requiring SSO, we were told that any users currently using email and password logins would simply be prompted to switch to SSO. If that’s not the case, let us know, so that can turn off SSO for our project to allow these users to log back in!

When you enable SSO in your organization any user must use the SSO to access any projects in this organization.

What you are describing sounds like Two-Factor Authentication (2FA) which can be enforced for a particular project/environment for users using email and password logins. 2FA is an identity and access management security method that requires two forms of identification to access resources. You can find more information in this documentation!

But I just look at your project and it is not set up either.

@Sarah_Wessel

Failure Logs

Please use email and password to access your <email-address> account.

Let’s get back to the failure. This error specifically happens when a user tries to connect with 0Auth2 (in our case Sign in with Google from the login page) but they registered/signed up using email and password logins.

• Can you please reach out to the user that encounters this issue to validate this mistake?
• If the user prefers to connect with Google you can send an email to our team so we can make the change.

To sum up (and respond to the SSO required), in your current configuration users can still connect using either Sign in with Google or Standard email and password login as you don’t have the SSO enabled in your organization. If you need some help to set up it for your project don’t hesitate to reach out to the Customer Success team as you’re a paying client.

Let me know if it helps.

Kind regards,
Morgan