In Google Password Manager and iCloud Keychain, Conditional Create (Automatic Passkey Upgrades) can make a passkey without extra user actions. On the other hand, Bitwarden currently shows a vault picker, so the user experience differs from other password managers. Could Bitwarden also auto-select the save target based on the most recent password autofill when Conditional Create is invoked?
The WebAuthn Level 3 Draft states that when mediation: "conditional" is used, prominent modal UI should not be shown, which suggests that automatically determining the save target from the recent autofill is the intended behavior.
That said, some users may not want Conditional Create, so it may be necessary to provide an option to disable this feature, as with other password management tools.
@conjLob … with “auto-select the last autofilled account…” you more or less meant “parallel to or directly following that last autofilled login process”, right?
Yes, that’s exactly what I meant. In most implementations, Conditional Create is accepted only within a short window in the same browsing context right after a password was autofilled. On the RP side, the common pattern is to call Conditional Create immediately after a successful password sign-in.
If it is okay to you, I changed the title now fromAuto-select the last autofilled account for Conditional CreatetoSupport “Conditional Create” (i.e. automatic passkey upgrade/creation – immediately after a login to a supporting account) to make the request (hopefully) a bit more clear.