Closed Bug 1814722 Opened 3 years ago Closed 3 years ago

The FIDO AppID extension is not handled properly when `security.webauthn.ctap2` is true

Categories

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

defect

Tracking

()

RESOLVED FIXED
111 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox109 --- unaffected
firefox110 --- unaffected
firefox111 --- fixed

People

(Reporter: jschanck, Assigned: jschanck)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

The FIDO AppID extension allows a relying party to request an assertion from a credential that was created using the legacy U2F javascript API. We seem to support this correctly in U2FHIDTokenManager but not in CTAPHIDTokenManager, i.e. not when security.webauthn.ctap2 is true.

Users can work around this by re-registering their security keys.

Duplicate of this bug: 1814859
Duplicate of this bug: 1814812

The following field has been copied from a duplicate bug:

Field Value Source
Regressed by bug 1752089 bug 1814812

For more information, please visit auto_nag documentation.

Keywords: regression
Regressed by: 1752089

Set release status flags based on info from the regressing bug 1752089

Attachment #9316235 - Attachment description: WIP: Bug 1814722 - Handle FIDO AppID extension in CTAPHIDTokenManager. r=keeler → Bug 1814722 - Handle FIDO AppID extension in CTAPHIDTokenManager. r=keeler
Pushed by jschanck@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3fb4400f7c37 Handle FIDO AppID extension in CTAPHIDTokenManager. r=keeler,supply-chain-reviewers
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: