Skip to main content

Passkeys and two-factor sign-in

A passkey lets people sign in with a fingerprint, their face or a device screen lock instead of typing a code, and it can replace the password altogether. Passkeys work next to authenticator apps and recovery codes. This page covers how people add and remove passkeys, how signing in works with and without a password, and what administrators can require, switch off or reset. People who only want the steps for their own account can read Account security.

What a passkey is​

The passkey lives on the person's device (a computer, a phone or a security key). MonoPbx stores only its public half, so nothing useful can be stolen from the server. Every passkey sign-in checks that it really is the person (fingerprint, face or PIN), which is why it counts as a second factor, or as two factors when it replaces the password.

Add, rename and remove a passkey​

Each person manages their own passkeys on Account security, in Me (the person's photo at the bottom of the sidebar), under Passkeys.

  1. Choose Add a passkey.
  2. Give it a name you will recognise, for example "Work laptop", and enter your current password.
  3. Choose Create passkey and follow the prompt of the browser: fingerprint, face, PIN or security key.

A person can have up to 20 passkeys. The list shows when each was added and when it was last used. Rename changes the name; Remove (and then Remove passkey) deletes it after the password is entered again.

If a browser cannot create passkeys, the page says so: use a current browser on a device with a screen lock or a security key.

Signing in​

Next to a password. After the e-mail and password, the sign-in page asks for a second step. A passkey replaces the code from the authenticator app: choose Use a passkey and confirm on the device. If the person has both an authenticator app and a passkey, both are offered (Use a passkey instead and Back to the passkey switch between them), and a recovery code always works.

Without a password. Choose Sign in with a passkey on the sign-in page. No e-mail or password is typed: the device offers the passkeys it holds for this web address and a fingerprint, face or PIN signs the person in.

One web address, one set of passkeys. A passkey belongs to the web address where it was created, such as acme.pbx.example.com or the company's own domain, and needs HTTPS with a domain name (an IP address does not work). If the company changes its web address, the old passkeys stop working until people add them again; passwords and authenticator apps keep working.

Authenticator apps next to passkeys​

People who prefer codes can still use an authenticator app: Set up an authenticator app under Two-step verification on Account security, then save the recovery codes. Passkeys and the app can be kept side by side, and either one satisfies the second step.

What administrators control​

On Security, in the Two-factor sign-in card (company administrators who may change settings):

  • Require two-factor sign-in for everyone, or require it for the holders of chosen roles. Covered users meet the rule with either an authenticator code or a passkey. A covered user who already has a passkey is not asked to set up an authenticator app; a covered user with neither is asked to set one up at the next sign-in.
  • Allow signing in with a passkey alone, on by default. Turn it off to always require the password first: the sign-in page then hides Sign in with a passkey, and passkeys keep working as the second step after the password.

When two-factor is required, a person cannot remove the last passkey if it is their only second step. The page says: add another passkey or an authenticator app first. The same applies to turning off the authenticator app.

Repeated wrong answers on the sign-in page, for passkeys as for passwords, lock the network address for that account for a while. See IP bans and the IP allow-list for how to see and lift blocks. Single sign-on and Duo are covered in Single sign-on; the overview of every protection is in Security and network access.

Recovery​

  • Lost a device. The person signs in with a recovery code or their authenticator app, then removes the lost passkey on Account security and adds a new one.
  • Recovery codes. They work as a second step for anyone. A person who has only passkeys can create a set on Account security.
  • Nothing left. An administrator opens the person on Users and chooses Reset passkeys, then confirms. This removes every passkey of that person and signs them out everywhere. They sign in with their password (and the authenticator app, if they have one) and add new passkeys. The action is recorded in the audit log.

Limits and notes​

  • Passkeys are for the web console. The MonoPhone mobile app does not offer them: it asks for an authenticator code or a recovery code.
  • Passkeys cannot be shared between company addresses, even of the same install.
  • A passkey is only as safe as the device that holds it: keep a screen lock on.
  • Passwords stay the default way in. Passkeys are optional unless an administrator requires a second factor, and then a passkey or an authenticator app is enough.
  • Single sign-on users sign in through their identity provider and follow its own rules.