Assertion requests don't filter out devices that don't hold a credential
Categories
(Core :: DOM: Web Authentication, enhancement, P3)
Tracking
()
People
(Reporter: git, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:158.0) Gecko/20100101 Firefox/158.0
Steps to reproduce
Steps to reproduce:
- Plug in two security keys, register a credential on a website with only one of them
- Sign in on this website with the security key
Firefox 159.0 on Arch Linux, two YubiKey 5 (FIDO2, PIN set).
Actual results
Both keys blink, I need to touch the right one to select it, then enter the PIN, then touch it again.
Expected results
Only the key holding the credential is used, like when a single key is plugged in.
The allow list is known before the selection, so a silent assertion (up=false) can tell which key holds the credential without any interaction. I opened a PR on authenticator-rs: https://github.com/mozilla/authenticator-rs/pull/387
Comment 1•21 days 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•17 days ago
•
|
||
The patch only changes the behaviour when using AppID, and isn't an issue otherwise.
Comment 3•17 days ago
•
|
||
Hmm, now after re-reading your patch, it's not clear what you're trying to fix, because what you're describing shouldn't be a problem.
Can you please provide a simple reproduction of the issue, including all the parameters used with navigator.credentials.create and .get.
PS: the patch for Bug 2081040 is planned to land in Firefox 160. So you probably haven't seen the impact of that just yet.
Updated•17 days ago
|
Updated•17 days ago
|
Description
•