Toolpack:Configure HTTPS certificates A - Revision history

Allyntree at 18:48, 13 November 2020

2020-11-13T18:48:31Z

2020-11-13T18:48:10Z

2020-11-13T18:47:46Z

2020-07-24T17:19:56Z

Steps

2020-07-24T17:19:27Z

Steps

2020-07-24T17:19:17Z

Steps

2020-07-24T17:19:00Z

Steps

2020-07-24T17:18:45Z

Applies to version(s): v2.9, v2.10, v3.0, v3.2

2020-07-24T17:18:23Z

Minor edits

2020-07-24T17:14:47Z

Applies to version(s): v2.9, v2.10, v3.0, v3.2

@@ Line 10: / Line 10: @@
 |}
 If you created a HTTP service using HTTPS and want to have an officially signed certificate, follow these steps
 . Activate the HTTPS on the unit to have the system generate a self-signed certificate.

@@ Line 10: / Line 10: @@
 |}
 If you created a HTTP service using HTTPS and want to have an officially signed certificate, follow these steps
 . Activate the HTTPS on the unit to have the system generate a self-signed certificate.

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:Configure HTTPS certificates}}
+{| class="wikitable"
-If you created a HTTP service using HTTPS and want to have a officially signed certificate, follow these steps
+|-
 == Steps ==

@@ Line 10: / Line 10: @@
 . Log in as root using SSH to your unit and go to /lib/tb/toolpack/pkg/ssl_certificate.
     cd /lib/tb/toolpack/pkg/ssl_certificate
 . Create a 'certificate signing request' form and private key using the following command:
     openssl req -out CSR.csr -new -newkey rsa:2048 -nodes -keyout privateKey.key
@@ Line 21: / Line 22: @@
     privateKey.key
 . Download the generated CSR.csr from your unit (using SCP) and sent it to your signing authority to get a signed certificate.
 . Once you have the signed certificate, upload it to your unit (using SCP) in the same directory as before.
 . Concatenate the private key and signed certificate and replace the contents of the file toolpack_cert.pem
      rm -f toolpack_cert.*
      cat privateKey.key <yoursignedcertificatefile>  > toolpack_cert.pem
 . Restart the Webportal process to load the new certificate.
      killall lighttpd

@@ Line 13: / Line 13: @@
     openssl req -out CSR.csr -new -newkey rsa:2048 -nodes -keyout privateKey.key
 You will be prompted for information.  One of the prompts is for the 'common name'. Set it to the URL that you will use to access the unit.  If an IP address is used, we strongly recommend it to either be static or 'reserved' in the DHCP.
 For example:
     https://192.168.130.3:12358  -> common name = 192.168.130.3

@@ Line 2: / Line 2: @@
 {{DISPLAYTITLE:Configure HTTPS certificates}}
-If you created a HTTP service using HTTPS and want to have a officially signed certificate, you can follow these steps
+If you created a HTTP service using HTTPS and want to have a officially signed certificate, can follow these steps
 == Steps ==