Closed Bug 1710730 Opened 4 years ago Closed 2 years ago

Add support for handling multiple attached security keys for web authentication

Categories

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

Product:
Core
Component:
DOM: Web Authentication
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: chk2dpg6hpekhufq, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.0.0 Safari/537.36

Steps to reproduce:

  1. I attached mutiple FIDO(2) security keys to my system
  2. I tried to login to a website with U2F authentication.

Actual results:

The browser is unable to make the right decision about which security key to use.

Expected results:

The browser should notice to the user that there are multiple security keys attached to the system and let the user decide which one to use in any specific U2F authentication scenario.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Web Authentication' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → DOM: Web Authentication
Product: Firefox → Core
Severity: -- → S3
Depends on: webauthn-ctap2
Priority: -- → P1

FWIW, this works with security.webauthn.ctap2 = true, which will be the default soon. I'll leave this open until we flip the pref.

Priority: P1 → P3
Depends on: enable-ctap2
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.