Home
Help CenterSign up for Frontegg

Enabling Passkeys

Suggest Edits

Enabling passkeys adds an extra layer of security to your account. Instead of relying solely on traditional password-based authentication, passkeys introduce an additional element, such as a hardware token or biometric data, making it harder for unauthorized access to occur. This enhanced security measure helps protect sensitive information and ensures a safer online experience.

📘

Passwordless Authentication

Learn more about Passkeys Authentication in the Authentication section.

What are passkeys?

Passkeys' authentication method includes the use of biometrics such as Touch ID, Face ID, and security key. It relies on the authentication method available on a user’s device. When you use your device's security features, you can ensure that your information is secure and easier for you to manage than both passwords and all the current methods of two-factor authentication.

Apple, Google, and Microsoft collaborated to create passkeys as a way to enhance authentication. By that, they allowed the consumer-standard FIDO and WebAuthN to be used.

The main benefits of passkeys are:

  1. Quicker - Biometrics make login quick and simple.
  2. Safer - Passekys are often tied to a specific device or user. This makes it more difficult for hackers to gain access to user accounts and sensitive information.
  3. Easy to use - Passkeys can be more convenient for users, as they do not have to remember complex passwords or visit an email box/ phone to get a one-time code.
  4. Synced with other devices - Passkeys allow users to access their sign-in credentials on many of their devices, even new ones, without having to re-enroll every device on every account.

How to add passkeys as a way of authentication?

Step 1 - Add passkeys to your sign-in page

  1. Go to the builder
  2. Go to the experience tab
  3. Choose the Login box section
  4. Enable the _Passkeys _toggle

This is how your sign-in page would look with the Sign in with passkey button:

Step 2 (optional) - Add an option to set up passkeys within the Admin Portal.
In order to let your users manage passkeys within your app in the Admin portal, follow the next steps;

  1. Go to builder
  2. Go to the experience tab.
  3. Choose the Admin portal tab.
  4. Enable “Privacy & Security” tab. (see note)
    For more information about integrating the Admin portal click here.

🚧

Limitations while testing locally

You cannot add your passkeys from the Privacy & Security if you running the app locally (e.g., on http://localhost:3000).

To set a passkey from your Privacy & Security tab, you need to have your own Custom Domain.

Step 3 - Publish

  1. Click the Review to publish button.
  2. Add a comment and click on Publish to development".
    Your changes are now ready in your Development environment. To test it further, go your Development environment and push your changes to deploy them. Learn more about your environments here.

User Login Flow with Passkeys

Once the passkeys are added to the sign-in page, users will be able to follow these steps to set up passkeys

  1. User will sign in to their account
  2. User will go to Passkeys set-up page
  3. User will set up passkeys by clicking the Use passkey button and following their device instructions.
  4. Users can decide whether they want to see the prompt again— They will see it only once by default.

  1. Manage passkeys within the Admin Portal
  • Go to the “Privacy & Security” tab
  • Click the "set up passkeys" button if passkeys are not set up already

Once the passkeys are set users can

  • Delete passkey by clicking the trash icon
  • View the last time passkeys were added.

Once the user set up passkeys (one of the two ways) then on their next sign-in they can enter the App by clicking “Sign in with passkey” on the Sign-in page.

Passkeys Restrictions

  1. MFA; Multi factor authentication is used to ensure second authentication method that is different from the main authentication. Our MFA methods include Authenticator apps, built in authenticators, SMS, and security key. In order to avoid a double use of WebAuthN authentication, we enforce different authentication methods.

    1. On the builder - You won't be able to add passkeys if you don't add "SMS" / "Authenticator apps" as MFA options for your users.
    2. On the sign-in flow - If users authenticated with "built in authenticators" / "security key" as a MFA method, they won't be able to view the prompt passkeys page.
    3. On the Admin Portal - If MFA is forced, users won't be able to set up Passkeys if they didn't set up SMS/Authenticator apps as MFA methods.

  2. SSO sign-in; Users that logged in with SSO won’t be able to set up passkeys. SSO is considered a secured authentication and when enabled it means that a user must sign in with SSO.

    1. On the sign-in flow - passkeys prompt page won't be visible
    2. On the Admin Portal - Passkeys section won't be visible.

Demonstration of login flow

  1. Set up passkey page - gif
    1. Sign in
    2. Set up passkeys within the passkeys set-up page
    3. Sign out
    4. Sign in with passkey

Update version

The feature is available from version
@frontegg/[email protected]
@frontegg/[email protected]
@frontegg/[email protected]
@frontegg/[email protected]

Going live checklist

  1. Add passkeys as an authentication method to the builder
  2. [Optional] - add Security & Privacy tab to the Admin portal to enable management of passkeys within the app
  3. Publish changes to development
  4. Update your app version to the version mentioned above
  5. Test passkeys on your development environment
  6. Push changes to production (or other env)

Updated about 1 month ago