Manually key selection and activating

[developStorm]

I'm trying to debug the credential creating process with this extension and there is an issue.

For instance, assume I created a virtual authenticator key1, created a credential, and registered it to the server. If I then go to creating another authenticator key2, I will not be able to create a credential for key2 if I wish to keep both key1 and key2 since now the extension will automatically activate both keys, and the key1 in the excludeCredentials will crash the creating process.

I'm hoping if you can support for selecting and activating key manually so that I can explicitly choose to activate key2 in the scenario.

Thanks!

[nsatragno]

Hi, thank you for your feedback!

I'm hoping if you can support for selecting and activating key manually so that I can explicitly choose to activate key2 in the scenario.

I'm assuming you want to select an authenticator and not a key, at least for the case where the relying party sends the credential IDs.

This is the limitation of the underlying DevTools Protocol we're using. There is a flag for every authenticator that sets whether it pretends that it was tapped or not but it can only be set when creating an authenticator for Reasons That Were Decided At The Time (tm). That means if you create two authenticators, they will both race for the tap. I agree this is a necessary feature for this extension to be (more) useful.

I have filed https://crbug.com/1086270 and will follow up with an update to the extension after that change. Feel free to start the issue there!

We also need something similar for empty allow credentials requests and resident credentials. Right now the virtual authenticator will pick the first credential but an actual user might select any. There's already a bug for that: https://crbug.com/991666

[developStorm]

want to select an authenticator and not a key

That's what exactly I want to say. Thanks for the follow-up!

[nsatragno]

I wanted to give an update for whoever stumbles into this issue: we added the ability to select which authenticator responds on chromium. However, this extension will soon be replaced by proper support in devtools - and you can try it right now by enabling experiments and ticking the webauthn experiment.