We are about to turn on SSO for our users, but would like to maintain the option of allowing a traditional sign up/in. With Universal Login, the option to type in a password disappears if the email domain matches an Identity Provider domain specified in Enterprise > Connection > SAML (or others) > [our connection] >Login Experience.
What’s the best practice for accommodating both the traditional sign in/up, and SSO, even if the email domain matches Identity Provider domain? IE: we’d like to give the user the option to use traditional sign-in as well as SSO.