WebAuthn: Difference between revisions

Moving #passkey #branding section to the higher section #Cybersecurity #WebAuthn #VulcanSphere
Line 54: Line 54:


== Background ==
== Background ==
FIDO2 is the successor to FIDO Universal 2nd Factor (U2F). Whereas U2F only supports multi-factor mode, having been designed to strengthen existing username/password-based login flows, FIDO2 adds support for single-factor mode. In multi-factor mode, the authenticator is activated by a test of ''user presence'', which usually consists of a simple button push; no password is required. In single-factor mode, the authenticator (''something you have'') performs ''user verification''.<ref>{{cite web |title=User Presence vs User Verification |url=https://developers.yubico.com/WebAuthn/WebAuthn_Developer_Guide/User_Presence_vs_User_Verification.html |access-date=19 February 2024}}</ref> Depending on the authenticator capabilities, this can be:<ref>{{Cite web|url=https://fidoalliance.org/specs/fido-v2.0-rd-20180702/fido-registry-v2.0-rd-20180702.html#user-verification-methods|title=FIDO Registry of Predefined Values|last1=Baghdasaryan|first1=Davit|last2=Hill|first2=Brad|date=2 July 2018|website=fidoalliance.org|publisher=FIDO Alliance|access-date=2019-06-16}}</ref>
FIDO2 is the successor to FIDO Universal 2nd Factor (U2F). Whereas U2F only supports multi-factor mode, having been designed to strengthen existing username/password-based login flows, FIDO2 adds support for single-factor mode. In multi-factor mode, the authenticator is activated by a test of ''user presence'', which usually consists of a simple button push; no password is required. In single-factor mode, the authenticator (''something you have'') performs ''user verification''.<ref>{{cite web |title=User Presence vs User Verification |url=https://developers.yubico.com/WebAuthn/WebAuthn_Developer_Guide/User_Presence_vs_User_Verification.html |access-date=19 February 2024}}</ref> Depending on the authenticator capabilities, this can be:<ref>{{Cite web|url=https://fidoalliance.org/specs/fido-v2.0-rd-20180702/fido-registry-v2.0-rd-20180702.html#user-verification-methods|title=FIDO Registry of Predefined Values|last1=Baghdasaryan|first1=Davit|last2=Hill|first2=Brad|date=2 July 2018|website=fidoalliance.org|publisher=FIDO Alliance|access-date=2019-06-16}}</ref>


Line 64: Line 65:


== Reasons for its design and standardization ==
== Reasons for its design and standardization ==
The W3C designed and standardized WebAuthn to solve or mitigate many issues that are inherent to traditional password-based authentication:
The W3C designed and standardized WebAuthn to solve or mitigate many issues that are inherent to traditional password-based authentication:


Line 83: Line 85:


== Overview ==
== Overview ==
Like its predecessor FIDO U2F, W3C Web Authentication (WebAuthn) involves a [[website]], a [[web browser]], and an authenticator:<ref name="W3C-WebAuthn-Level-1" />
Like its predecessor FIDO U2F, W3C Web Authentication (WebAuthn) involves a [[website]], a [[web browser]], and an authenticator:<ref name="W3C-WebAuthn-Level-1" />


Line 114: Line 117:


== Support ==
== Support ==
[[File:Bitwarden Passkey window screenshot.png|thumb|upright=1.2|Example of WebAuthn implementation ([[Bitwarden]] for [[Pixiv]])]]
[[File:Bitwarden Passkey window screenshot.png|thumb|upright=1.2|Example of WebAuthn implementation ([[Bitwarden]] for [[Pixiv]])]]
The WebAuthn Level&nbsp;1 standard was published as a W3C Recommendation by the [[Web Authentication Working Group]] on 4 March 2019.<ref name="W3C-WebAuthn-Level-1" /><ref name="W3C-WebAuthn-announce" /><ref>{{Cite web |url=https://venturebeat.com/2019/03/04/w3c-approves-webauthn-as-the-web-standard-for-password-free-logins/ |title=W3C Approves WebAuthn as the Web Standard for Password-Free Logins |last=Protalinski |first=Emil |date=4 March 2019}}</ref> WebAuthn is supported by [[Google Chrome]], [[Mozilla Firefox]], [[Microsoft Edge]], [[Safari (web browser)|Apple Safari]]<ref name="W3C-WebAuthn-announce" /> and [[Opera (web browser)|Opera]].<ref>{{cite web |title=Can I use Web Authentication API? |url=https://caniuse.com/#feat=webauthn |access-date=7 March 2019}}</ref>
The WebAuthn Level&nbsp;1 standard was published as a W3C Recommendation by the [[Web Authentication Working Group]] on 4 March 2019.<ref name="W3C-WebAuthn-Level-1" /><ref name="W3C-WebAuthn-announce" /><ref>{{Cite web |url=https://venturebeat.com/2019/03/04/w3c-approves-webauthn-as-the-web-standard-for-password-free-logins/ |title=W3C Approves WebAuthn as the Web Standard for Password-Free Logins |last=Protalinski |first=Emil |date=4 March 2019}}</ref> WebAuthn is supported by [[Google Chrome]], [[Mozilla Firefox]], [[Microsoft Edge]], [[Safari (web browser)|Apple Safari]]<ref name="W3C-WebAuthn-announce" /> and [[Opera (web browser)|Opera]].<ref>{{cite web |title=Can I use Web Authentication API? |url=https://caniuse.com/#feat=webauthn |access-date=7 March 2019}}</ref>
Line 138: Line 142:


The API does not allow direct access to or manipulation of private keys, beyond requesting their initial creation.
The API does not allow direct access to or manipulation of private keys, beyond requesting their initial creation.
== Passkey branding ==
''Passkey'' is the [[de facto]] [[technical language|non-technical]] term for a WebAuthn credential.<ref name="docsrs-webauthnrs" /><ref name="imperialviolet-webauthn" /> It is widely used in situations where jargon is unhelpful, such as consumer marketing, and most user interfaces that support WebAuthn use only ''passkey'' to refer to WebAuthn credentials.<ref name="arstechnica-not-usable" />
When Apple first introduced passkeys to the public in 2022,<ref>{{cite news |last1=Clemons |first1=Taylor |title=WWDC 2022: Apple announces Passkey feature to eliminate passwords across platforms |url=https://www.zdnet.com/article/wwdc-2022-apple-announces-passkey-feature/ |access-date=4 July 2025 |publisher=ZD Net |date=6 June 2022}}</ref> they emphasized their first-party platform integrations. This, combined with the lack of clear communication from other industry leaders, led some to speculate that passkeys were proprietary to Apple (this was not the case).<ref>{{cite news |last1=Shakir |first1=Umar |title=Reminder: passkeys are not just from Apple |url=https://www.theverge.com/2022/8/5/23293643/apple-passkeys-fido-alliance-passwordless-google-microsoft |access-date=4 July 2025 |publisher=The Verge |date=6 August 2022}}</ref> As browsers and websites began to implement WebAuthn, the inconsistent feature-sets resulted in a variety of understandings of what exactly counted as a passkey. Some people assumed that a passkey required management by a platform authenticator, or needed synchronization using the cloud. A better definition is that a passkey is any WebAuthn credential managed by any WebAuthn authenticator.<ref name="docsrs-webauthnrs" /> This definition covers most of what different vendors refer to and accept as ''passkeys''.


== Reception ==
== Reception ==
Line 163: Line 173:


*"...the implementation seems to have failed the "make it easy for users" test, which in my view is the whole point of passkeys. I have been using [[public key cryptography]] for 30-plus years...If I find passkeys confusing to use, it doesn’t bode well for more typical users."<ref>https://www.theregister.com/2024/11/17/passkeys_passwords/</ref>{{dash}}Bruce Davie – November 17, 2024 [[The Register]]
*"...the implementation seems to have failed the "make it easy for users" test, which in my view is the whole point of passkeys. I have been using [[public key cryptography]] for 30-plus years...If I find passkeys confusing to use, it doesn’t bode well for more typical users."<ref>https://www.theregister.com/2024/11/17/passkeys_passwords/</ref>{{dash}}Bruce Davie – November 17, 2024 [[The Register]]
== Passkey branding ==
''Passkey'' is the [[de facto]] [[technical language|non-technical]] term for a WebAuthn credential.<ref name="docsrs-webauthnrs" /><ref name="imperialviolet-webauthn" /> It is widely used in situations where jargon is unhelpful, such as consumer marketing, and most user interfaces that support WebAuthn use only ''passkey'' to refer to WebAuthn credentials.<ref name="arstechnica-not-usable" />
When Apple first introduced passkeys to the public in 2022,<ref>{{cite news |last1=Clemons |first1=Taylor |title=WWDC 2022: Apple announces Passkey feature to eliminate passwords across platforms |url=https://www.zdnet.com/article/wwdc-2022-apple-announces-passkey-feature/ |access-date=4 July 2025 |publisher=ZD Net |date=6 June 2022}}</ref> they emphasized their first-party platform integrations. This, combined with the lack of clear communication from other industry leaders, led some to speculate that passkeys were proprietary to Apple (this was not the case).<ref>{{cite news |last1=Shakir |first1=Umar |title=Reminder: passkeys are not just from Apple |url=https://www.theverge.com/2022/8/5/23293643/apple-passkeys-fido-alliance-passwordless-google-microsoft |access-date=4 July 2025 |publisher=The Verge |date=6 August 2022}}</ref> As browsers and websites began to implement WebAuthn, the inconsistent feature-sets resulted in a variety of understandings of what exactly counted as a passkey. Some people assumed that a passkey required management by a platform authenticator, or needed synchronization using the cloud. A better definition is that a passkey is any WebAuthn credential managed by any WebAuthn authenticator.<ref name="docsrs-webauthnrs" /> This definition covers most of what different vendors refer to and accept as ''passkeys''.


== See also ==
== See also ==