WebAuthn: Difference between revisions

m →Overview: expand para on biometrics
→Background: add new section; remove redundant content
Line 2: Line 2:


'''WebAuthn''' ('''Web Authentication''') is a [[web standard]] published by the [[World Wide Web Consortium]] (W3C).<ref name="W3C-WebAuthn-Level-1">{{cite web |editor1-last=Balfanz |editor1-first=Dirk |editor2-last=Czeskis |editor2-first=Alexei |editor3-last=Hodges |editor3-first=Jeff |editor4-last=Jones |editor4-first=J.C. |editor5-last=Jones |editor5-first=Michael B. |editor6-last=Kumar |editor6-first=Akshay |editor7-last=Liao |editor7-first=Angelo |editor8-last=Lindemann |editor8-first=Rolf |editor9-last=Lundberg |editor9-first=Emil |title=Web Authentication: An API for accessing Public Key Credentials Level&nbsp;1 |url=https://www.w3.org/TR/2019/REC-webauthn-1-20190304/ |publisher=World Wide Web Consortium (W3C) |date=4 March 2019 |accessdate=4 March 2019}}</ref><ref>{{cite web |url=https://www.w3.org/blog/webauthn/ |title=Web Authentication Working Group |accessdate=2018-05-11 |publisher=W3C}}</ref> WebAuthn is a core component of the [[FIDO2 Project]] under the guidance of the [[FIDO Alliance]].<ref name="fido2">{{cite web|url=https://fidoalliance.org/fido2/|title=FIDO2 Project|publisher=FIDO Alliance|accessdate=2018-05-11}}</ref> The goal of the project is to standardize an interface for [[public-key authentication]] of users to web-based applications and services.
'''WebAuthn''' ('''Web Authentication''') is a [[web standard]] published by the [[World Wide Web Consortium]] (W3C).<ref name="W3C-WebAuthn-Level-1">{{cite web |editor1-last=Balfanz |editor1-first=Dirk |editor2-last=Czeskis |editor2-first=Alexei |editor3-last=Hodges |editor3-first=Jeff |editor4-last=Jones |editor4-first=J.C. |editor5-last=Jones |editor5-first=Michael B. |editor6-last=Kumar |editor6-first=Akshay |editor7-last=Liao |editor7-first=Angelo |editor8-last=Lindemann |editor8-first=Rolf |editor9-last=Lundberg |editor9-first=Emil |title=Web Authentication: An API for accessing Public Key Credentials Level&nbsp;1 |url=https://www.w3.org/TR/2019/REC-webauthn-1-20190304/ |publisher=World Wide Web Consortium (W3C) |date=4 March 2019 |accessdate=4 March 2019}}</ref><ref>{{cite web |url=https://www.w3.org/blog/webauthn/ |title=Web Authentication Working Group |accessdate=2018-05-11 |publisher=W3C}}</ref> WebAuthn is a core component of the [[FIDO2 Project]] under the guidance of the [[FIDO Alliance]].<ref name="fido2">{{cite web|url=https://fidoalliance.org/fido2/|title=FIDO2 Project|publisher=FIDO Alliance|accessdate=2018-05-11}}</ref> The goal of the project is to standardize an interface for [[public-key authentication]] of users to web-based applications and services.
WebAuthn can be used in a single-factor capacity, whereby the user does not have to provide any additional information, such as username and passwords. However, for additional security, the party asking for authentication can still require those characteristics, effectively making this a [[multi-factor authentication]] scheme. Optionally, this can also be combined with other authentication factors, such as gestures or [[biometric]] verification, which improves overall security, while it is still unnecessary for users to type in long, complex strings of characters.


WebAuthn can be implemented in a variety of different ways, since the underlying cryptographic operations are performed by an [[authenticator]], which is an abstract functional model that is mostly agnostic on the details of how the key material is managed. This makes it possible to implement WebAuthn purely in software, but also to make use of a processor's [[trusted execution environment]] or a [[Trusted Platform Module]] (TPM). Sensitive cryptographic operations can also be offloaded to external hardware tokens that can in turn be accessed via [[USB]], [[Bluetooth Low Energy]], or [[near-field communication]]s (NFC). This, in general, is more secure, as private key material is at no time accessible to software running on the host machine. The communication with external hardware tokens is designed to work with the [[Client to Authenticator Protocol]] (CTAP), making WebAuthn effectively backward compatible with the FIDO [[Universal 2nd Factor]] (U2F) standard.
WebAuthn can be implemented in a variety of different ways, since the underlying cryptographic operations are performed by an [[authenticator]], which is an abstract functional model that is mostly agnostic on the details of how the key material is managed. This makes it possible to implement WebAuthn purely in software, but also to make use of a processor's [[trusted execution environment]] or a [[Trusted Platform Module]] (TPM). Sensitive cryptographic operations can also be offloaded to external hardware tokens that can in turn be accessed via [[USB]], [[Bluetooth Low Energy]], or [[near-field communication]]s (NFC). This, in general, is more secure, as private key material is at no time accessible to software running on the host machine. The communication with external hardware tokens is designed to work with the [[Client to Authenticator Protocol]] (CTAP), making WebAuthn effectively backward compatible with the FIDO [[Universal 2nd Factor]] (U2F) standard.


The WebAuthn Level&nbsp;1 standard was published as a W3C Recommendation on 4&nbsp;March 2019.<ref name="W3C-WebAuthn-announce">{{cite web |title=W3C and FIDO Alliance Finalize Web Standard for Secure, Passwordless Logins |url=https://www.w3.org/2019/03/pressrelease-webauthn-rec.html.en |publisher=[[World Wide Web Consortium]] (W3C) |accessdate=4 March 2019 |date=4 March 2019}}</ref> A Level&nbsp;2 specification is under development.<ref name="W3C-WebAuthn-Level-2">{{cite web |editor1-last=Balfanz |editor1-first=Dirk |editor2-last=Czeskis |editor2-first=Alexei |editor3-last=Hodges |editor3-first=Jeff |editor4-last=Jones |editor4-first=J.C. |editor5-last=Jones |editor5-first=Michael B. |editor6-last=Kumar |editor6-first=Akshay |editor7-last=Liao |editor7-first=Angelo |editor8-last=Lindemann |editor8-first=Rolf |editor9-last=Lundberg |editor9-first=Emil |title=Web Authentication: An API for accessing Public Key Credentials Level&nbsp;2 |url=https://w3c.github.io/webauthn/ |publisher=World Wide Web Consortium (W3C) |accessdate=6 March 2019}}</ref>
The WebAuthn Level&nbsp;1 standard was published as a W3C Recommendation on 4&nbsp;March 2019.<ref name="W3C-WebAuthn-announce">{{cite web |title=W3C and FIDO Alliance Finalize Web Standard for Secure, Passwordless Logins |url=https://www.w3.org/2019/03/pressrelease-webauthn-rec.html.en |publisher=[[World Wide Web Consortium]] (W3C) |accessdate=4 March 2019 |date=4 March 2019}}</ref> A Level&nbsp;2 specification is under development.<ref name="W3C-WebAuthn-Level-2">{{cite web |editor1-last=Balfanz |editor1-first=Dirk |editor2-last=Czeskis |editor2-first=Alexei |editor3-last=Hodges |editor3-first=Jeff |editor4-last=Jones |editor4-first=J.C. |editor5-last=Jones |editor5-first=Michael B. |editor6-last=Kumar |editor6-first=Akshay |editor7-last=Liao |editor7-first=Angelo |editor8-last=Lindemann |editor8-first=Rolf |editor9-last=Lundberg |editor9-first=Emil |title=Web Authentication: An API for accessing Public Key Credentials Level&nbsp;2 |url=https://w3c.github.io/webauthn/ |publisher=World Wide Web Consortium (W3C) |accessdate=6 March 2019}}</ref>
== Background ==
FIDO2 is the successor of the FIDO Universal 2nd Factor (U2F) legacy protocol. FIDO2 authentication has all the advantages of U2F&mdash;the primary difference is that a FIDO2 authenticator is a multi-factor authenticator (''something you have'').
A FIDO2 authenticator may be used in either single-factor mode or multi-factor mode. In single-factor mode, the authenticator is activated by a test of user presence (TUP), which usually consists of a simple button push. In multi-factor mode, the authenticator is activated by either a PIN (''something you know'') or a biometric (''something you are'').
In any case, FIDO2 authentication does not require a traditional password. A memorized secret (the PIN) is still required for user verification but that secret is not shared with the website. The PIN is stored on the authenticator and never leaves the authenticator. Moreover, a single PIN works with all websites.
In addition to the PIN, a FIDO2 authenticator may support a biometric (typically a fingerprint). Like the PIN, the biometric is stored on the authenticator and never leaves the authenticator.
The PIN and biometric on the authenticator work together like the PIN and biometric on your smartphone. In practice, a fingerprint is used to provide access to the device but occasionally fingerprint access fails, in which case the device falls back on the PIN. A FIDO2 authenticator with both PIN and biometric works similarly.
Since no shared secret is transmitted over the network, FIDO2 authentication is sometimes called '''passwordless web authentication'''. Although the term is somewhat misleading (due to the PIN) it tends to be used interchangeably with the more accurate term ''FIDO2 authentication''.


== Overview ==
== Overview ==
Line 27: Line 39:
WebAuthn does not strictly require a roaming hardware authenticator. Alternatively, a software authenticator (implemented on a smartphone, e.g.) or a platform authenticator (i.e., an authenticator implemented directly on the WebAuthn Client Device) may be used. Relevant examples of platform authenticators include Windows Hello<ref>{{cite web |last1=Simons |first1=Alex |title=Secure password-less sign-in for your Microsoft account using a security key or Windows Hello |url=https://www.microsoft.com/en-us/microsoft-365/blog/2018/11/20/sign-in-to-your-microsoft-account-without-a-password-using-windows-hello-or-a-security-key/ |publisher=[[Microsoft]] |accessdate=6 March 2019 |date=November 20, 2018}}</ref> and the [[Android operating system]].<ref>{{cite web |title=Android Now FIDO2 Certified, Accelerating Global Migration Beyond Passwords |url=https://fidoalliance.org/android-now-fido2-certified-accelerating-global-migration-beyond-passwords/ |publisher=[[FIDO Alliance]] |accessdate=6 March 2019 |location=BARCELONA |date=February 25, 2019}}</ref>
WebAuthn does not strictly require a roaming hardware authenticator. Alternatively, a software authenticator (implemented on a smartphone, e.g.) or a platform authenticator (i.e., an authenticator implemented directly on the WebAuthn Client Device) may be used. Relevant examples of platform authenticators include Windows Hello<ref>{{cite web |last1=Simons |first1=Alex |title=Secure password-less sign-in for your Microsoft account using a security key or Windows Hello |url=https://www.microsoft.com/en-us/microsoft-365/blog/2018/11/20/sign-in-to-your-microsoft-account-without-a-password-using-windows-hello-or-a-security-key/ |publisher=[[Microsoft]] |accessdate=6 March 2019 |date=November 20, 2018}}</ref> and the [[Android operating system]].<ref>{{cite web |title=Android Now FIDO2 Certified, Accelerating Global Migration Beyond Passwords |url=https://fidoalliance.org/android-now-fido2-certified-accelerating-global-migration-beyond-passwords/ |publisher=[[FIDO Alliance]] |accessdate=6 March 2019 |location=BARCELONA |date=February 25, 2019}}</ref>


The illustrated flow relies on PIN-based user verification, which, in terms of usability, is only a modest improvement over ordinary password authentication. In practice, a FIDO2 authenticator (''something you have'') is activated by either a PIN (''something you know'') or a biometric (''something you are''). The use of [[biometric]]s for user verification can significantly improve the usability of WebAuthn.{{Citation needed|date=March 2019}}
The illustrated flow relies on PIN-based user verification, which, in terms of usability, is only a modest improvement over ordinary password authentication. In practice, the use of [[biometric]]s for user verification can significantly improve the usability of WebAuthn.{{Citation needed|date=March 2019}}


== Support ==
== Support ==