Version 1 by Bren Eckles
on Mar 29, 2018 18:29.

compared with
Current by Joey Byers
on Sep 27, 2019 12:20.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
It's not actually necessary to store the output revocation-list file (e.g., {{crl_01.pem}}) in the same directory as the key and certificate files, but having it there makes it a lot easier to find later on (when you will copy certificate and revocation-list files to your client machines).
# To make future file copying more convenient, make a copy of your certificate file under the name by which it will be known on the client machines. Embedding a trivial serial number in the copied filename will make it much easier to distinguish which file is which later on, so *change the command shown here to choose the next number in sequence at your site*. The first such copy command might look like this if using a self-signed certificate:
cd /usr/local/groundwork/apache2/conf
cp -p server.crt server_01.pem
If using a chained certificate that contains a root and server certificate, it may look like this:
cd /usr/local/groundwork/apache2/conf
cat server-ca-root.crt server.crt > server_01.pem
# Finish setting up Apache and Java on the GroundWork Monitor server to use HTTPS, as documented in the [How to enable HTTPS] Bookshelf page. That will include bouncing both {{apache}} and {{gwservices}}, as listed at the end of that procedure.