[webauthn] Discourage bootstrapping new credential provider as part of CREATE call (#2432)

rlin1 has just created a new issue for https://github.com/w3c/webauthn:

== Discourage bootstrapping new credential provider as part of CREATE call ==
## Current Challenge
On platforms there might be multiple credential managers installed, but often not all of them have been "bootstrapped".
Sometimes, explicitly calling "create" for creating a passkey is part of the sign-in flow (when conditional create cannot be used) when transitioning users from legacy authentication to passkeys.

This leads to good conversion rate if the create process is low friction. It leads to bad UX when a new credential manager (that was not bootstrapped already) is being used.
Bootstrapping a passkey provider should be triggered independently.

## Proposed Change

Add a flag (additional PublicKeyCredentialHint) for "create" that discourages bootstrapping new credential managers - instead prefer one of the credential managers that was already bootstrapped.

Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2432 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 2 June 2026 08:18:45 UTC