2026-03-13 16:03 UTC
Replies (7)
-
@neidu3@sh.itjust.works 2026-03-13 16:08
Not _that_ strange. Different users may belong to different groups which may have different authentication backends. The associated authentication method is brought up once a username has been provided.
-
@IcedRaktajino@startrek.website 2026-03-13 16:09
And the auto-submitting TOTP entry form where you're apparently not allowed to make a typo. And obscuring the TOTP number like it's a password or state secret.
-
@bamboo@lemmy.blahaj.zone 2026-03-13 16:31
This is because of Enterprise Single Sign On. You can try this for yourself by going to https://gmail.com/ and enter the email of a public person at a large org, for example the CEO of Doordash (`tony@doordash.com`). After you enter the email, you get sent to Doordash's employee portal to authenticate. Based on the email you provide, Gmail has to figure out if you need to provide a password to gmail itself or if the email authenticates another way.
-
@ricecake@sh.itjust.works 2026-03-14 02:11
That ones because users like choice. They need to look up who you are to know how you've chosen to authenticate. At least, that's how it started. Some could be doing it because the big kids are, but that's why the big kids do. And they support choice because businesses want to use their login infrastructure and refuse to share. So you enter "user@businessOrUniversity.com.edu" and it forwards you to your institutional login.
-
@kibiz0r@midwest.social 2026-03-13 16:48
1Password handles this gracefully
-
@helvetpuli@sopuli.xyz 2026-03-14 13:30
That's there to support routing to an identity provider for SAML2 SSO.
-
@mimavox@piefed.social 2026-03-13 23:29
Came here to say that! For the love of God, stop with this nonsense!