Skip to Content
Platform Ontology

Software passkey for test tools

Test tools can add a pretend passkey device to a browser so sign in flows run without hardware.

When you are signed inWhile you use it

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

APIWebDriver Virtual Authenticator commands; CDP WebAuthn.addVirtualAuthenticator, addCredential, setUserVerified
How access is grantednone
What the user seesNone; only the driver can turn it on
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsFor the test session
How to take it backClose the session or remove the authenticator
Inside an iframeApplies to the whole browser session

Typical flow

  1. Test tool starts a virtual authenticator in the browser
  2. Tool adds or accepts credentials through the protocol
  3. Page runs the normal WebAuthn calls
  4. Authenticator answers with no hardware

Data you get

Shape: object
How often: test session

FieldTypeUnitRangePrecision
protocolenumNonectap2 or u2fNot listed
transportenumNoneinternal, usb, nfc or bleNot listed
hasUserVerificationbooleanNonewhether the virtual device passes user checksNot listed
credentialslistNonecredentials added by the toolNot 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

TypeExampleApps
developerA QA team tests passkey sign in in CI with a virtual authenticator.Selenium, Playwright
securityA security team tests how a site handles invalid passkey answers.None named
bankingA bank tests its sign in pages without hardware keys.None named
enterpriseA platform team checks a passkey rollout against many browsers.None named
shoppingA store tests passkey checkout on staging.None named
productivityA 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

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

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits0Rough 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

Sources

How well checked: Inferred from related behavior.

On this page