Can only resolve one WebAuthn request at a time |
||
Issue descriptionChrome Version: 69.0.3446.0 (Official Build) canary (64-bit) OS: MacOS 10.13.4 What steps will reproduce the problem? (1) Navigate to webauthndemo.appspot.com in two side by side windows (2) Click Register new credential in one window, then the other (3) Resolve a request by touching a security key (4) Navigate back to other window and note that request is active and unresolvable What is the expected result? I'm not sure of the desired behavior, I would assume either: Non-active window is resolved with an error or Navigating back to non-active window resumes request and allows resolution with inserted security key What happens instead? Non-resolved window (it seems inconsistent whether the active window or non-active window get resolved) continues waiting and is unresolvable until timeout occurs or security key is unplugged and replugged.
,
Jun 1 2018
(My mental model was that the active window would be resolved first)
,
Jun 1 2018
This is not related to focus checks. You'll get the same result if you do simultaneous GetAssertion requests in multiple tabs in the same window. What happens is that we start servicing all requests at the same time, so they start fighting for the same device, get weird responses, and declare the SK to be broken forever, until only one request survives. When you replug the SK it will be discovered as a new device and tried again.
,
Jun 1 2018
Balazs, I thought at one time you had it so that one could issue 10 requests and then resolve all 10 in some order. What changed? |
||
►
Sign in to add a comment |
||
Comment 1 by kpaulhamus@chromium.org
, Jun 1 2018