The latest articles on DEV Community by susi (@bucker). https://dev.to/bucker https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F386701%2F9c11c95e-b90a-444e-8594-92a122ff8b69.png https://dev.to/bucker en susi Sun, 21 Feb 2021 07:44:25 +0000 https://dev.to/bucker/why-separate-username-and-password-into-two-pages-1aoh https://dev.to/bucker/why-separate-username-and-password-into-two-pages-1aoh <p>Answer: Because the username/password isn't the only way to login.</p> <p>If we want to support both <a href="https://en.wikipedia.org/wiki/Single_sign-on">SSO</a> and username/password login, the first thing we need to do is to check which way the user has been using.</p> <p>For example, if the user is using the Google SSO, then you check the email, make sure he/she is using the Google SSO, then show the Google SSO option.</p> <p><a href="https://bradfrost.com/blog/post/dont-get-clever-with-login-forms/">For someone who thinks the username/password is the best way to login</a>, it's not surprising that they feel cumbersome and "user-unfriendly" for splitting the username and password into two pages.</p> <p>Still, if you want a single page to handle both SSO and username/password login, based on <a href="https://www.twilio.com/blog/why-username-and-password-on-two-different-pages">this article</a>, there are two options:</p> <ol> <li>Show SSO options after the user types the email</li> <li>Optional password field</li> </ol>