Monday, March 21, 2016

accounts - How do you prevent users from getting confused with multiple login options?


I came across this question in a closed LinkedIn group. I think it's a great one and since it's hidden from search engines, I decided to bring it to the outside world.


Some users don't visit your website/application as frequently as others and are bound to forget their login credentials. When accounts are created with a simple username-password combo, you offer the Forgot your login details? option.


However, what do you do when you also use 3rd-party authentication APIs (e.g. OAuth or OpenID)?



  • What is the most effective way to help returning users remember the service they used to create their accounts?

  • How do you prevent them from creating a duplicate account via another authentication service?


I realize the answer might be more technical than design and might have include some back-end code. If that's the case, please simply link to the documentation and don't post the code here.




Answer



Well I found this interesting article from Luke Wroblewski https://bagcheck.com/blog/02-design-solutions-for-new-log-in-problems


Essence:


enter image description here


enter image description here


enter image description here


Ideally, there is a nifty way that the "Forget how you signed up, Enter user name: - This is in sync with existing patterns and it looks best to start with. Next, Step 2 -is what my concern area where on typing "Luke" it provides a auto-populated results, which is against privacy, and I do recommend that to be a simple plain text box. Step 3, is cool that it brings only the related Sign-on engine and takes away unwanted buttons or platforms.


This certainly address the issues that is existing with SSO.


No comments:

Post a Comment

technique - How credible is wikipedia?

I understand that this question relates more to wikipedia than it does writing but... If I was going to use wikipedia for a source for a res...