Remove the U2F DOM API once Chrome and Google websites have deprecated it
Categories
(Core :: DOM: Web Authentication, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox114 | --- | fixed |
People
(Reporter: dveditz, Assigned: jschanck)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Chrome plans to deprecate the U2F interface starting in M95 with warnings, disabling it by default in Spring 2022, and fully removing it in Summer 2022. We supported this legacy API primarily because the Google website required it to register credentials; we will be happy to follow suit.
See their Intent to Deprecate thread:
https://groups.google.com/a/chromium.org/g/blink-dev/c/xHC3AtU_65A
(Note that the dates in the original June 11 mail were pushed out in a later September mail)
Or clearer:
https://developer.chrome.com/blog/deps-rems-95/#deprecate-u2f-api-cryptotoken
we should watch to make sure they don't slip further as we get closer to the cut-off dates.
We will do this in two steps:
- change the
security.webauth.u2f
pref tofalse
when they have disabled it (Spring) - remove the code once they've fully removed it (after August 2022)
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Chrome has fully deleted the U2F API with Chrome 109 (currently in Beta: https://chromiumdash.appspot.com/commit/c86cc6503c9944784099b0d540d3e68bc3bb1f6f).
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Updated•2 years ago
|
Comment 4•2 years ago
|
||
bugherder |
Description
•