Please, I beg you, put your username and password inputs on the same page. Don't make me click a button to go to the password entry then another to login.
@arch I agree in the general case, but I do use multiple services for work that optionally support SSO and they have to know your username (i.e. email address) to know if your organization is one of the ones that use SSO so they necessarily have to split it onto multiple pages. Presumably there are too many SSO options/they want to accommodate the lowest common denominator user, so they can't have SSO options to click on the sign in page in the first place.
@arch I hate this so much. Keepass can auto-input username/password for enhanced security and all this does is make things not as easy unless I want to go in and start manipulating how the auto-inputs work.
@arch its soooo stupid when you have a password manager and this breaks auto-type and makes you have to add {ENTER}{DELAY 3000} in between the two fields.......
another stupid annoyance is when the window title is just "login" so my password manager can't detect what website i'm actually logging in to and i have to select the entry manually....... ugh
@arch I agree with you. I've seen this as a pattern for federated login flows, especially in Microsoft shops — [@]contoso.com automatically redirects to Microsoft 365, while [@]gmail.com just shows a password field.
The alternative pattern I've seen (e.g., Jira) is to have buttons for "Log in with { Microsoft, Google, Facebook }" and then reject domains that require federation when you try using a password.
I am not sure of all the considerations between those two.
Add comment