As of v2.48, sign-in now starts with your email address then continues based on your account's authorization process. This change was made to reduce the amount of times users unknowingly attempted to sign in via an unsupported method. If SSO is enabled for the instance, admins and above are routed through SSO first when attempting to log in and will only see a password option if SSO fails (to prevent lock outs if SSO is set up incorrectly).
Blue Raccoon
•
May 16, 2025
We have regulatory requirements that we meet using SSO. E.g. conditional access policies on AzureAD which enforce device compliance, location, etc. If that can simply be bypassed, then SSO is simply there for convenience of sign-in, but offers zero security benefit.
Log in to comment and vote
Comments2
Kristen Wasko
Oct 22
As of v2.48, sign-in now starts with your email address then continues based on your account's authorization process. This change was made to reduce the amount of times users unknowingly attempted to sign in via an unsupported method. If SSO is enabled for the instance, admins and above are routed through SSO first when attempting to log in and will only see a password option if SSO fails (to prevent lock outs if SSO is set up incorrectly).
Blue Raccoon
May 16, 2025
We have regulatory requirements that we meet using SSO. E.g. conditional access policies on AzureAD which enforce device compliance, location, etc. If that can simply be bypassed, then SSO is simply there for convenience of sign-in, but offers zero security benefit.