Closed Bug 1737205 Opened 3 years ago Closed 2 years ago

Remove the U2F DOM API once Chrome and Google websites have deprecated it

Categories

(Core :: DOM: Web Authentication, task, P3)

task

Tracking

()

RESOLVED FIXED
114 Branch
Tracking Status
firefox114 --- fixed

People

(Reporter: dveditz, Assigned: jschanck)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

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:

  1. change the security.webauth.u2f pref to false when they have disabled it (Spring)
  2. remove the code once they've fully removed it (after August 2022)

Chrome has fully deleted the U2F API with Chrome 109 (currently in Beta: https://chromiumdash.appspot.com/commit/c86cc6503c9944784099b0d540d3e68bc3bb1f6f).

Depends on: 1804579
Blocks: 1804651
Depends on: 1809333
Depends on: 1814983
Blocks: 1817040
Assignee: nobody → jschanck
Status: NEW → ASSIGNED
Pushed by jschanck@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9acbf3389238 remove the legacy U2F javascript API. r=dveditz,webidl,smaug
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: