1893366 - WebAuthn no longer works with github.com

Status: NEW

(Firefox for Android :: WebAuthn, defect, P3)

Description

[Jonathan Almeida [:jonalmeida]]

Steps to reproduce

1. Sign-in to github.com
2. Add Fenix as a passkey (Settings > Password and authentication > Add a passkey).
3. Sign out of github.com.
4. Sign-in using passkeys.

Expected behaviour

You should see the pass key setup in the native list.

Actual behaviour

You do not see the pass key in the native list - "No passkeys available".

Device information

• Firefox version: 127a1
• Android device model: Pixel 6a
• Android OS version: Android 14

Any additional information?

• Github was one of the sites tested against when the feature was first implemented.
• Github notes on their website: "This browser or device is reporting partial passkey support."

Comment 1

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

This bug has been marked as a regression. Setting status flag for Nightly to affected.

Comment 2

[Pascal Chevrel:pascalc]

Joe, is that really a P3/S3 if a feature stopped working, are we sure that it only affects fenix? What about 126? Thanks

Comment 3

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

The bug is marked as tracked for firefox127 (nightly). We have limited time to fix this, the soft freeze is in 8 days. However, the bug still isn't assigned, has low priority and has low severity.

:jmahon, could you please find an assignee, increase the priority and increase the severity for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Comment 4

[John Schanck [:jschanck]]

Passkey support is not quite the same as WebAuthn support, and it's true that we do not have full Passkey support on Android. That will be fixed in Bug 1862132.

That said, you should be able to register a Passkey after setting security.webauthn.webauthn_enable_android_fido2.residentkey to true. Could you try that?

Comment 5

[Jonathan Almeida [:jonalmeida]]

(In reply to John Schanck [:jschanck] from comment #4)

Passkey support is not quite the same as WebAuthn support, and it's true that we do not have full Passkey support on Android. That will be fixed in Bug 1862132.

That said, you should be able to register a Passkey after setting security.webauthn.webauthn_enable_android_fido2.residentkey to true. Could you try that?

I re-tested this with the flag enabled and the bug still persists (even after restarting the browser once the pref was set).

Comment 6

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

This is a reminder regarding comment #3!

The bug is marked as tracked for firefox127 (nightly). We have limited time to fix this, the soft freeze is in 2 days. However, the bug still isn't assigned and has low priority.

Comment 7

[Haik Aftandilian [:haik]]

@Jonathan, now that bug 1862132 has been fixed in Nightly, are you still able to reproduce this on the latest Nightly?

Comment 8

[Jonathan Almeida [:jonalmeida]]

Redirecting to krosylight who I had reported this bug on behalf of.

Note that the latest release of nightly isn't up yet while the Play Store app reviewing is backed up. We need to wait for at least 128.0a1.20240516091652 based on the changeset that landed for the bug in comment 7.

Comment 9

[Kagami Rosylight [:saschanaz] (they/them)]

Sorry for the late response! We had a long weekend in Germany and also I was waiting for the update to happen. Sadly I still see the same issue; with the steps in the comment #0 I still see "No passkeys available" with the build ID 20240516214828.

What does work is:

4. Sign in with password
5. Tap "Use passkey" on 2FA screen

But that already works on the stable channel.

Comment 10

[Haik Aftandilian [:haik]]

I confirmed with Kagami that the problem in comment 0 also reproduces on stable therefore this is not a regression.

The working sequence on comment 9 may be a clue as to what is happening here.

Comment 11

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

This is a reminder regarding comment #3!

The bug is marked as tracked for firefox127 (beta). We have limited time to fix this, the soft freeze is in 14 days. However, the bug still isn't assigned and has low priority.

Comment 12

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

This is a reminder regarding comment #3!

The bug is marked as tracked for firefox127 (beta). We have limited time to fix this, the soft freeze is in 8 days. However, the bug still isn't assigned and has low priority.

Comment 14

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

The severity field for this bug is set to S3. However, the following bug duplicate has higher severity:

• Bug 1900350: S2

:jmahon, could you consider increasing the severity of this bug to S2?

For more information, please visit BugBot documentation.

Comment 15

[Mira Lobontiu (Android QA)]

This is also reproducible on Nightly 129.0a1 from 6/12, and Beta 128.0b1, with Google Pixel 6 (Android 14), and Oppo Find N2 Flip (Android 14).
NOT reproducible with Samsung Galaxy S24 (Android 14).

Comment 16

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

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.