From fbda31f8971d2f99a5c63b5f1e3d7f626faebce9 Mon Sep 17 00:00:00 2001 From: Brennan Kinney <5098581+polarathene@users.noreply.github.com> Date: Sat, 3 Sep 2022 19:04:33 +1200 Subject: [PATCH] docs: clarify chromes deprecation of u2f in favor of webauthn (#3949) --- docs/content/en/roadmap/active/webauthn.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/content/en/roadmap/active/webauthn.md b/docs/content/en/roadmap/active/webauthn.md index d195c5ee7..08040a167 100644 --- a/docs/content/en/roadmap/active/webauthn.md +++ b/docs/content/en/roadmap/active/webauthn.md @@ -14,7 +14,7 @@ aliases: - /r/webauthn --- -[WebAuthn] requires urgent implementation as it is being deprecated by Chrome. It is a modern evolution of the +[WebAuthn] requires urgent implementation as [Chrome removed support of their U2F API since August 2022][chrome-removed-u2f]. It is a modern evolution of the [FIDO U2F] protocol and is very similar in many ways. It even includes a backwards compatability extension called the [FIDO AppID Extension] which allows a previously registered [FIDO U2F] device to be used with the protocol to authenticate. @@ -64,6 +64,7 @@ registration. [FIDO U2F]: https://fidoalliance.org/specs/u2f-specs-master/fido-u2f-overview.html [WebAuthn]: https://www.w3.org/TR/webauthn-2/ +[chrome-removed-u2f]: https://developer.chrome.com/blog/deps-rems-95/#deprecate-u2f-api-cryptotoken [Passwordless Login]: https://www.w3.org/TR/webauthn-2/#client-side-discoverable-public-key-credential-source [Conveyancing Preference]: https://www.w3.org/TR/webauthn-2/#enum-attestation-convey [User Verification Requirement]: https://www.w3.org/TR/webauthn-2/#enum-userVerificationRequirement