Skip to main content

Passkey Creation for Non-MFA User Accounts

Non-MFA users logging in via desktop and mobile browsers, follow a standard login flow where they are offered to append a passkey.
  • macOS
  • Windows
  • iOS
  • Android
non-mfa-append-macos.png

macOS passkey append, non-MFA accounts

NOTE: The blue background indicates product-native steps (e.g., verification code). Passkey creation is seamlessly embedded in your product journey.
1

Login when user has no passkeys

  • User enters their identifier (email/username) on the login page.
2

Fallback to traditional login method

  • If no passkey exists for the account, the system falls back to the traditional login method (username and password).
3

Passkey append process initiates

  • Once the user is logged in via traditional method, they are offered an option to create a passkey for future logins.
4

Passkey append process continues

  • User continues with the passkey creation process.
4.a. OS-native biometric prompt appears
  • OS biometric prompt modal appears asking the user to authenticate using fingerprint, face, or PIN for secure sign-in.
  • User successfully authenticates via biometrics.
4.b. Passkey creation successful
  • User successfully creates a passkey and it is now linked with the user account for the respective web-app.
4.c. System prompts for user verification
  • The user is prompted to verify their account via a code sent through email or SMS.
4.d. Successful second factor verification
  • User successfully completes the second factor verification.
4.e. Redirection to app dashboard
  • User is redirected to the app dashboard.
5

Skips the passkey append process

  • User skips the passkey setup process and continues with the second factor verification.
5.a. System prompts for user verification
  • The user is prompted to verify their account via a code sent through email or SMS.
5.b. Successful second factor verification
  • User successfully completes the second factor verification.
5.c. Redirection to app dashboard
  • User is redirected to the app dashboard.
I