Ondřej SurýDec 9
Repeat after me: Separating username and password fields on separate (fucking responsive) page WILL NOT INCREASE A FUCKING SECURITY IN ANY WAY! IT WILL JUST MAKE THE PASSWORD MANAGERS TO WORK WORSE AND THUS IT WILL FUCKING DECREASE THE SECURITY!!!
Show threadCMDR Yojimbosan 🅅⁂Dec 9
@ondrej One reasonable possibility for the pattern is systems that implement SSO login flows for *some* users, and they don't want an SSO-bound user to spend time worrying about inputting a password that may indeed not exist.
They need to evaluate the username to decide whether to prompt for a password at all.
Which password managers are causing you problems?
Show threadÖlbaumDec 9
@yojimbo It’s not the password manager that is causing problems, it’s the web site.
@ondrej
Show threadCMDR Yojimbosan 🅅⁂
@oscherler @ondrej I'm using Bitwarden and 1Password, and although I've encountered many sites that split the username and password onto separate screens, most of them work just fine. Some of them do cause failures to follow the flow, and I have to select the password from a dropdown, like I do for the password. I see this as a UX fail and agree that's annoying, but I do not directly as a decrease in security. I may have misunderstood something, and I'm happy to be corrected.
Dec 10 at 2:34amWeb