Multiple hardware security keys plugged in but cannot use either
Categories
(Core :: DOM: Web Authentication, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox114 | --- | fixed |
People
(Reporter: jacob.bednarz, Unassigned)
References
Details
Attachments
(1 file)
53.14 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
Prior to the webauthn DOM improvements, when I navigated to any site that needed to read my hardware security key and had two plugged in, Firefox would ask which one I would like to use. Now, I get the prompt to select one of the devices however, attempting to touch or interact with either doesn't work.
Steps:
- Plug in two hardware security keys
- Visit a website that requires hardware key interaction (I tested with Gmail)
- You are prompted to select one of the devices
Actual results:
Despite being prompted to select one, you cannot use either until you unplug one or reinsert one.
Expected results:
You are able to interact with either, thus selecting which one you wish to use for the hardware security key step.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Web Authentication' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
presumably the same issue as bug 1829490
Reporter | ||
Comment 3•2 years ago
|
||
thank you for finding other tickets 🙇 I tried but still a n00b with the search. do we want to close this as a duplicate and I can add a note to the other bug that this is still present in 113?
Comment 4•2 years ago
|
||
I'm not yet sure, if this is a duplicate of bug 1829490.
However, I can reproduce this one, and I have (hopefully) a fix: https://github.com/mozilla/authenticator-rs/pull/256
Updated•2 years ago
|
Comment 6•2 years ago
|
||
Sorry, I see why msirringhaus wasn't sure if this was a duplicate of the other bug now. I'll re-open until we confirm.
Comment 7•2 years ago
|
||
The fix from Comment 4 landed with Bug 1830944.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•