From 74bbb102ad43b581dd8dd1c64b5c90d082ffd92e Mon Sep 17 00:00:00 2001 From: Randall Mason Date: Tue, 22 Feb 2022 09:49:06 -0600 Subject: [PATCH] Note that WebAuthn is enabled in the same way as U2F. --- ...on.md => Enabling-U2F-(and-FIDO2-WebAuthn)-authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename Enabling-U2F-authentication.md => Enabling-U2F-(and-FIDO2-WebAuthn)-authentication.md (77%) diff --git a/Enabling-U2F-authentication.md b/Enabling-U2F-(and-FIDO2-WebAuthn)-authentication.md similarity index 77% rename from Enabling-U2F-authentication.md rename to Enabling-U2F-(and-FIDO2-WebAuthn)-authentication.md index b106bfa..ed54a7f 100644 --- a/Enabling-U2F-authentication.md +++ b/Enabling-U2F-(and-FIDO2-WebAuthn)-authentication.md @@ -1,4 +1,4 @@ -To enable U2F authentication, you must be serving vaultwarden from an HTTPS domain with a valid certificate (Either using the included +To enable U2F and FIDO2 WebAuthn authentication, you must be serving vaultwarden from an HTTPS domain with a valid certificate (Either using the included HTTPS options or with a reverse proxy). We recommend using a free certificate from Let's Encrypt. After that, you need to set the `DOMAIN` environment variable to the same address from where vaultwarden is being served: