Closed Bug 1813383 Opened 3 years ago Closed 2 years ago

Webauthn (YubiKey) not working on Firefox Nightly for Android

Categories

(Firefox for Android :: WebAuthn, defect)

Firefox 111
All
Android
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: fischerfelix06, Unassigned)

Details

Steps to reproduce:

  1. Open google.com in new private tab
  2. Enter username and password
  3. Choose security key as 2nd factor

Actual results:

Play Services dialog is opened, touching the key makes it close (as usual), but the website does not proceed the login.

Expected results:

After touching the key, there should be a success banner on the webiste.
Tried it in Firefox stable and it worked perfectly.

Can you confirm that the preferences security.webauth.u2f and security.webauthn.ctap2 are both set to false?

Yes, the are

Thanks. It would also be helpful to know if it works with security.webauth.u2f set to true. Also, if you happen to be a desktop nightly user, it would help to know if authenticating to the same account on desktop works.

Authentication on desktop works as expected (Firefox Nighly 111.0a1 on Linux).
Neither setting security.webauth.u2f nor security.webauth.ctap2 to true changed anything.

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)

I have also confirmed a similar problem.
I am using WebAuthn fingerprint login (with User-Agent changed to Chrome) on Yahoo! Japan, but Firefox Nightly (112.0a1 Build #2015935267) fails without fingerprint dialogs and I can only log in using other authentication methods.
Firefox Beta (111.0b5 Build #2015935227) works fine.

I think it's fixed on latest build of Firefox Nightly (112.0a1 Build #2015935459).
Perhaps this is due to a problem with the link below, which has been fixed.
https://github.com/mozilla-mobile/firefox-android/pull/974

Flags: needinfo?(cpeterson)

Comment 7 is correct, this was a bug in our build system that should be fixed already.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.