Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross-window Virtual Authenticator Database #2117

Open
sshmaxime opened this issue Aug 9, 2024 · 4 comments
Open

Cross-window Virtual Authenticator Database #2117

sshmaxime opened this issue Aug 9, 2024 · 4 comments

Comments

@sshmaxime
Copy link

sshmaxime commented Aug 9, 2024

Description

As of now, addVirtualAuthenticator seems to be window restricted (correct me if I'm wrong / inaccurate).
Therefore, I need to transfer my credentials from window to window (and more precisely from virtualAuthenticator to virtualAuthenticator). Is this the expected behavior ? If so why is that ?

Related Links

https://www.w3.org/TR/webauthn-2/#sctn-automation-virtual-authenticators

@sshmaxime sshmaxime changed the title Cross-(window/session) Virtual Authenticator Database Cross-window Virtual Authenticator Database Aug 9, 2024
@timcappalli
Copy link
Member

@sshmaxime I don't think there's anything in the linked section that specifies this behavior. Is this question more about a specific implementation in a user agent(s)?

@sshmaxime
Copy link
Author

@timcappalli Well, all I know is that when creating a virtual authenticator (VA) on Chrome, those VA are window restricted and the so call database is therefore specific to each window. Do you think this is more something on Chrome's side ?

@pascoej
Copy link
Contributor

pascoej commented Sep 11, 2024

I think WebKit doesn't attach the virtual authenticator database to the window, but rather the web view associated with the automation session.

I don't see anything at a glance that defines this behavior.

@sshmaxime
Copy link
Author

Hey @pascoej, I'm currently running my test on a Chrome instance and didn't had the time yet to check how it works within a WebKit browser but since you mentioned it, it seems that it works the same way in Chrome or WebKit. It's a bit odd imho and makes it hard to develop with it. So this issue would be more browser related if I understood correctly, right ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
@pascoej @timcappalli @sshmaxime and others