From 026d1cb03e17c5cb958d1ead660bb37eb1a665b0 Mon Sep 17 00:00:00 2001 From: Jeremy Lin Date: Thu, 18 Feb 2021 01:29:44 -0800 Subject: [PATCH] Updated Private CA and self signed certs that work with Chrome (markdown) --- Private-CA-and-self-signed-certs-that-work-with-Chrome.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Private-CA-and-self-signed-certs-that-work-with-Chrome.md b/Private-CA-and-self-signed-certs-that-work-with-Chrome.md index 2c9744f..7454830 100644 --- a/Private-CA-and-self-signed-certs-that-work-with-Chrome.md +++ b/Private-CA-and-self-signed-certs-that-work-with-Chrome.md @@ -1,3 +1,7 @@ +:warning: The vast majority of users should not use this method, as it requires loading a cert on each of your devices, which is both error-prone and requires future maintenance. Instead, focus your energy on obtaining real certs via [Let's Encrypt](https://letsencrypt.org/getting-started/). This can even work if your bitwarden_rs instance is not on the public Internet ([[example|Running-a-private-bitwarden_rs-instance-with-Let's-Encrypt-certs]]). + +--- + To get bitwarden working properly with self-signed certificates, Chrome needs the certificate to include the domain name in the alternative name field of the certificate. Create a CA key (your own little on-premise Certificate Authority):