This is an automated email from the ASF dual-hosted git repository.

gstein pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/steve.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 5140b65  add section on establishing trust within Chrome
5140b65 is described below

commit 5140b6551606152659e93bc84d339617913f0377
Author: Greg Stein <[email protected]>
AuthorDate: Wed Nov 5 00:34:35 2025 -0600

    add section on establishing trust within Chrome
---
 v3/server/certs/README.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/v3/server/certs/README.md b/v3/server/certs/README.md
index 08ca222..2f1d8b0 100644
--- a/v3/server/certs/README.md
+++ b/v3/server/certs/README.md
@@ -61,3 +61,17 @@ It will expire on 29 December 2027 🗓
 
 Adjust the `config.yaml` to refer to these new files. The default 
`config.yaml.example`
 config assumes the generated files are moved under the `server/certs` 
directory.
+
+## Browser Trust
+
+TBD: _more solutions besides Chrome_
+
+### Chrome Browser
+
+This is a self-signed certificate which is usually rejected by the Chrome 
browser.
+To correct this, select the "Settings" menu option, then "Privacy and 
Security".
+Within that pane, select "Manage certificates" which will open a new tab.
+Now select the "Import" button for "Trusted Certificates" and choose the `.pem`
+that was just generated. Should be `localhost.apache.org+3.pem` (not the key!).
+
+This should now provide trust to localhost for your dev/test operation.

Reply via email to