1
Allow configuring WebAuthn userVerification (currently hardcoded to "discouraged")
Source: dani-garcia/vaultwarden#7621 · opened by @ilvoen
Currently, userVerification in the WebAuthn challenge response is hardcoded to "discouraged". This means biometric FIDO2 keys (e.g. fingerprint sensors) never actually verify the biometric — the sensor just acts as a touch button, and any finger works.
It would be great to have an option (env var or admin panel setting) to set userVerification to "preferred" or "required", so biometric security keys can actually enforce fingerprint matching as part of the WebAuthn 2FA flow.
Use case: using a FIDO2 security key with a fingerprint sensor as a 2FA method, expecting the fingerprint to be verified — but currently any touch on the sensor is accepted regardless of whose finger it is.
It would be great to have an option (env var or admin panel setting) to set userVerification to "preferred" or "required", so biometric security keys can actually enforce fingerprint matching as part of the WebAuthn 2FA flow.
Use case: using a FIDO2 security key with a fingerprint sensor as a 2FA method, expecting the fingerprint to be verified — but currently any touch on the sensor is accepted regardless of whose finger it is.
No pledges yet. Be the first to back this.
Comments
Similar requests
Additional configuration for hardening 2FA
2 votes · 0 comments
Add support for Bitwarden-style passkey login (WebAuthn / PRF)
3 votes · 0 comments
[Docs] Example caddy configuration breaks Webauthn login
3 votes · 0 comments
Feature: Configurable default KDF type for new user registrations
1 vote · 0 comments
Support log in and decrypt with passkeys
90 votes · 0 comments
No comments yet.