1814983 - Cannot register a security key with Google when legacy U2F API is disabled

Status: RESOLVED FIXED

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

Description

[John Schanck [:jschanck]]

I'm not able to register a security key with Google when security.webauth.u2f is false. We made this the default in Bug 1809333, which landed in Nightly 111.

To reproduce

• Set security.webauth.u2f to false
• Visit https://myaccount.google.com/two-step-verification/security-keys
• Click "Add a security key"
• Select "Physical USB or NFC key"
• Click "Next"

After a few seconds, a small error message in the bottom left of the page says "The extension is not installed".

If I register a key with security.webauth.u2f set to true, I am able to use it with both settings of security.webauth.u2f and both settings of security.webauthn.ctap2.

I suspect that we may need to implement the googleLegacyAppIdSupport WebAuthn extension mentioned in Google's intent to deprecate and remove the U2F API.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 2

[Martin Kreichgauer]

I suspect that we may need to implement the googleLegacyAppIdSupport WebAuthn extension mentioned in Google's intent to deprecate and remove the U2F API.

That is not the case, Google should be able to enroll security keys with regular WebAuthn in Firefox. I'm looking into what we can do to fix this from the Google side.

Comment 3

[Donal Meehan [:dmeehan]]

Setting 111 to since the regressor 1809333 was backed out

Comment 4

[John Schanck [:jschanck]]

The problem has been fixed on Google's end.