- From: Matthew Miller via GitHub <noreply@w3.org>
- Date: Thu, 19 Feb 2026 18:17:52 +0000
- To: public-webauthn@w3.org
I'm trying to write this PR to also achieve Martin's desired end state of the Virtual Authenticator API defaulting into a "synced passkey" mode instead of the API's current "security key" mode. @kreichgauer and @nsatragno, can you take a look at this PR with an eye on if these proposed changes would move us to that end state **if** a subsequent PR were to update **Add Virtual Authenticator** endpoint's `defaultBackupEligibility` argument to instead default to `true`? Right now it defaults to `false`: <img width="763" height="80" alt="Screenshot 2026-02-19 at 10 13 44 AM" src="https://github.com/user-attachments/assets/94957d4a-4097-487d-a9b1-074c641b71e4" /> I'm thinking of a migration path for RPs with existing tests built around current Virtual Authenticator API behavior. I _think_ we can make it as simple as updating their calls to the **Add Virtual Authenticator** endpoint to add `defaultBackupEligibility: false` to get their tests passing again 🤔 -- GitHub Notification of comment by MasterKale Please view or discuss this issue at https://github.com/w3c/webauthn/pull/2382#issuecomment-3929020923 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 February 2026 18:17:53 UTC