Troubleshoot User Interfaces for Sign-In
This page offers troubleshooting tips for user interfaces for sign-in in relation to implementation of support for passkeys.
Create a single user interface for synced and device-bound passkeys
For organizations who already support security keys, how to build the most usable interface for both synced and device-bound passkeys might not be obvious.
Steps to reproduce
- Sign in to a service that supports synced and device-bound passkeys on security keys.
- Notice which user interfaces are used to create, view, and edit both passkey types.
- Compare their approaches to the FIDO Alliance design pattern Passkey Management UI: Best Practices for Combining All Passkey Types.
Guidance
Follow the guidance in the FIDO Alliance design pattern Passkey Management UI: Best Practices for Combining All Passkey Types.
Related resources
- FIDO Alliance design pattern Passkey Management UI: Best Practices for Combining All Passkey Types
Disabling autofill can lead to issues
Autofill ensures the highest success for people who sign in with a passkey. Autofill makes passkey sign-in fast and efficient. If autofill is turned off people can still sign in with a passkey but this requires additional steps.
Steps to reproduce
- Sign in to a service that supports autofill for passkeys.
- Sign out.
- Turn autofill off in your browser settings.
- Sign in to the same service.
- Notice the differences in the sign in process when autofill is turned off.
Guidance
Follow the guidance in the FIDO Alliance design pattern Sign in with a passkey.
Related resources
- FIDO: Sign in with a passkey design pattern
Sign in with a passkey buttons might lead to challenges
Some organizations that support passkeys have not implemented autofill. These organizations add a Sign in with a passkey button to their user interface. However, many end users do not know to look for this button. End users might also forgot they have a passkey. In other cases, end users might have a passkey they created in a native mobile app and do not think to look for a Sign in with a passkey button on that organization's website.
Additionally, end users who never created a passkey for the organization might try to use the Sign in with a passkey button. When this occurs, the end user is not authenticated because they have no passkey.
Steps to reproduce
- Imagine you are an end user and forgot that you have a passkey for an organization.
- Imagine how easy it is to not discover a Sign in with a passkey button.
- Or, imagine selecting the Sign in with a passkey button if you don't have a passkey.
Guidance
Follow the guidance in the FIDO Alliance design pattern: Sign in with a passkey.
