Discover how to design secure and user-friendly authentication experiences for software applications in this 28-minute talk by Heather Downing from Okta. Learn industry best practices for creating more acceptable authentication processes, identify pitfalls to avoid, and gain insights into human perceptions of security to elevate your app's user experience. Explore 15 essential rules for user sign-in, including inline email validation, streamlined password reset procedures, and the implementation of two-step authentication. Understand the importance of reducing cognitive load, leveraging password managers and on-device authentication, and offering Single Sign-On options. Gain valuable knowledge on designing persistent logins, managing user sessions, and creating intuitive journeys that prioritize user needs. Master the art of balancing security with usability to create an auth experience that truly caters to human users.
Building an Auth Experience for Humans - Best Practices and User-Friendly Design
Overview
Syllabus
Building an Auth Experience for Humans
This is for making auth SUCK LESS.
15 Rules for User Sign In
Apply inline validation for the email field
Reset password should carry the email into the new form
Offer password reset on the third try
Send a password reset link
Allow password managers to capture the user login credentials
On mobile apps, allow users to use their on-device authentication to login
Single Sign On (SSO) as a login option
Two-step authentication should be a norm for sites that contain sensitive information
Understand user's cognitive load for deeper navigation and design'outs' for errors
Persistent login should be the norm for non-sensitive sites
Don't force the user to login if, without login, the user can complete the journey
Upon login, if the user has items from a previous session, OVERWRITE IT!
Prompt account creation after the primary journey has been completed
Status links should not ask for logins (i.e. orders)
Abandoned Carts links should not prompt for login
Visibility of system status
Match between system and the real world
User control and freedom
Consistency and standards
Error prevention
Recognition rather than recall
Flexibility and efficiency of use
Aesthetic and minimalist design
diagnose, and recover from
Help and documentation
Cloud Identity is the house and the doorframe. You design the door.
Don't wait for a designer to take care of your users.
Taught by
Okta
