Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
WebAuthn is a technology that lets a browser log you in with a fingerprint or a key. Its full name is Web Authentication, and the W3C sets it as a standard. A service only has to call the entry point, an API, that the browser provides in order to support a fingerprint check or a security key.
How does Web Authentication work?
Think of a shared key reader in a hotel that accepts the cards of different companies. Because the shape of the reader is fixed, cards of different kinds can be used in the same way.
WebAuthn has two moments: registration and login. At registration, the service sends a challenge, and the authenticator creates a new key pair and returns the public key. At login, the service sends a new challenge, the authenticator signs it with the private key and returns it, and the service checks it with the public key it holds.
An authenticator may be built into a phone or computer, or attached from outside, for example by USB. The W3C specification binds the sites where a key can be used to the domain of the site where it was registered. Measures against improper login after introduction are collected under unauthorized access measures. The free URL check sees only the outside of your site and cannot confirm how your login is built.
Why does Web Authentication matter?
Because no password is used, it is harder to suffer the damage from reuse, guessing, and leaks. Because the key is bound to the domain, it also holds up against the method of making people type into a look-alike fake site.
A site that supports WebAuthn carries less of the burden of storing passwords and less risk of a leak. On the other hand, it needs to manage public keys, to use each challenge only once, and to design a recovery procedure. These are hard to build yourself, so use a proven library and do not skip the checks that the specification requires.
Related terms
- FIDO2: an open standard, set by an industry body, for logging in without a password
- Passkey (WebAuthn): the user-facing name for the FIDO mechanism
- Passwordless authentication: the general name for ways to log in without typing a password
- Biometric authentication: checking identity by body features such as a fingerprint or face
Next step
If your own service has a login, you can consider supporting WebAuthn as an option alongside passwords. Decide the recovery procedure at the same time. The free URL check shows only what is visible from outside, and we take questions on the design in a free consultation.
Frequently asked questions
Is my fingerprint data sent to the service when I use WebAuthn?
It is not. The match of a fingerprint or face is done inside the user's device. What reaches the service is the result of the device signing with a key.
What happens in a browser that does not support WebAuthn?
The user cannot log in, so keep another way of checking identity for environments that do not support it. Before you introduce it, test whether it really works on the browsers and devices your users have.
Frequently asked questions
Is my fingerprint data sent to the service when I use WebAuthn?
It is not. The match of a fingerprint or face is done inside the user's device. What reaches the service is the result of the device signing with a key.
What happens in a browser that does not support WebAuthn?
The user cannot log in, so keep another way of checking identity for environments that do not support it. Before you introduce it, test whether it really works on the browsers and devices your users have.