Software passkey for test tools
Test tools can add a pretend passkey device to a browser so sign in flows run without hardware.
The WebAuthn spec defines a WebDriver extension for virtual authenticators. Chrome exposes it through the DevTools Protocol WebAuthn domain and Selenium and Playwright expose it to scripts. A test or agent can register and use passkeys with no phone or security key. A site cannot call this from a page; it is a tool level control.
What it can and can't do
What the user does: None. A developer turns it on from the test tool
It can
- Create a software authenticator in tests
- Register and sign in with passkeys in CI
- Control user verification results
- Check a sign in flow end to end
It cannot
- Be used by a normal web page
- Fool a site that checks attestation against known devices
- Replace a person's approval in real accounts
- Work on a locked down browser
How it differs between platforms: It is a driver feature, not a web API. Sites that require hardware attestation reject the virtual device.
Browser support
Version notes
- Chrome: Through the DevTools Protocol WebAuthn domain and ChromeDriver
- Edge: Chromium based
- Firefox: Driver support varies; verify for your version
- Safari: Driver support varies; verify for your version
How a site asks for it
| API | WebDriver Virtual Authenticator commands; CDP WebAuthn.addVirtualAuthenticator, addCredential, setUserVerified |
| How access is granted | none |
| What the user sees | None; only the driver can turn it on |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | For the test session |
| How to take it back | Close the session or remove the authenticator |
| Inside an iframe | Applies to the whole browser session |
Typical flow
- Test tool starts a virtual authenticator in the browser
- Tool adds or accepts credentials through the protocol
- Page runs the normal WebAuthn calls
- Authenticator answers with no hardware
Data you get
Shape: object
How often: test session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
protocol | enum | None | ctap2 or u2f | Not listed |
transport | enum | None | internal, usb, nfc or ble | Not listed |
hasUserVerification | boolean | None | whether the virtual device passes user checks | Not listed |
credentials | list | None | credentials added by the tool | Not listed |
Technical limits
- Driver only
- Not allowed by sites that check attestation
- Coverage differs by browser
The story
What it is
A pretend security key that a test tool plugs in so sign in tests can run on any computer.
For you
You never see it. It is a tool for testers. It lets teams check that passkey sign in works without handing out hardware.
For makers
Use it for tests only. In agent products, a virtual authenticator must not stand in for a person's approval on a real account.
Where you see it
| Type | Example | Apps |
|---|---|---|
| developer | A QA team tests passkey sign in in CI with a virtual authenticator. | Selenium, Playwright |
| security | A security team tests how a site handles invalid passkey answers. | None named |
| banking | A bank tests its sign in pages without hardware keys. | None named |
| enterprise | A platform team checks a passkey rollout against many browsers. | None named |
| shopping | A store tests passkey checkout on staging. | None named |
| productivity | A SaaS team runs passkey tests on every release. | None named |
Risks
- Could be used to script real sign ins if misused
- Not a page API
What the platform says
- Chrome for Developers: Emulate authenticators. Docs show how DevTools adds a virtual authenticator to test passkeys.
Good uses and abuse
Legitimate uses
- Passkey testing
- Release checks
Known abuse
- Scripted sign ins by agents that should hand off to a person
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 0 | Rough identifying entropy, when known |
History
- 2019, Chrome: WebAuthn domain added to the DevTools Protocol and ChromeDriver
- 2024, spec: Virtual authenticators described in the WebAuthn spec WebDriver extension
Related capabilities
Related
- Passkeys and WebAuthn sign in. Can sign you in with a passkey after your fingerprint, face or PIN
- Passkey availability checks. Can tell whether the device is ready for passkeys
- Passkey on a nearby phone (hybrid). Can sign you in with a passkey on a phone, with no passkey on the computer
- Automation (webdriver) flag. Can tell if Selenium, Playwright, or Puppeteer is controlling the browser
Sources
- Chrome DevTools: emulate authenticators
- WebAuthn WebDriver extension
- Selenium: virtual authenticator
How well checked: Inferred from related behavior.