WebAuthn: Difference between revisions
No edit summary |
No edit summary |
||
| Line 72: | Line 72: | ||
== Overview == | == Overview == | ||
The WebAuthn standard provides a mechanism for a device or a program, known as the "authenticator") to verify a user's identity to a website through their web browser by confirming that the user possesses the device.<ref name="W3C-WebAuthn-Level-1" /> To do this in a secure manner, the standard defines two events, the registration ceremony and the authentication ceremony. During these events the authenticator communicates with the website through the web browser to register itself as a device the user possesses and proves to the website that the user still possesses the device respectively.<ref name="W3C-WebAuthn-Level-1" /> | |||
===Authentication=== | ===Authentication=== | ||
| Line 110: | Line 98: | ||
The attestation type specified in the JavaScript determines the trust model. For instance, an attestation type called self-attestation may be desired, for which the trust model is essentially [[trust on first use]]. | The attestation type specified in the JavaScript determines the trust model. For instance, an attestation type called self-attestation may be desired, for which the trust model is essentially [[trust on first use]]. | ||
=== Level 3 === | |||
WebAuthn Level 3 introduces several capabilities beyond authentication alone. The PRF (Pseudo-Random Function) extension allows a passkey to derive encryption keys, enabling it to help protect encrypted data such as backups without a separate password.<ref name="enpass-webauthn3">{{Cite web |title=What Is WebAuthn Level 3 & How Does Enpass Support It? |url=https://www.enpass.io/blog/security/what-is-webauthn-level-3-how-does-enpass-support-it/ |publisher=Enpass |date=23 July 2026 |access-date=20 August 2026}}</ref> Related Origin Requests (ROR) let a single passkey be used across multiple domains belonging to the same organization, reducing the need for duplicate credentials.<ref name="enpass-webauthn3" /> The specification also added a section addressing the privacy implications of using WebAuthn credentials across origins, including risks associated with cross-origin iframes.<ref>{{Cite web |title=[L3 REC] Transition Request Draft |url=https://github.com/w3c/webauthn/issues/2399 |publisher=GitHub |website=w3c/webauthn |access-date=20 August 2026}}</ref> | |||
== Support == | == Support == | ||