REDACTIVE - Using self-signed certificates

Objective

Needing to use a self-signed certificate for REDACTIVE Enterprise.

Procedure

Prerequisite: openssl installed

1. Run CMD as an Administrator
2. Start self-signed SSL generation:
   

   openssl req -newkey rsa:2048 -nodes -keyout domain.key -x509 -days 365 -out domain.crt

3. Answer the questions when prompted by openssl and make sure to use the fully qualified domain name of the REDACTIVE service when asked for "Common Name (e.g. server FQDN...)"
   

   Example:

   redactive.example.com

4. Copy or move the generated domain.crt and domain.key files to a folder on the REDACTIVE server
5. Login to REDACTIVE admin:

   http://localhost:9000/admin

6. Select the Network tab and check the Enabled box in the HTTPS section
7. Enter the FQDN that will be used to access the REDACTIVE service in the top box (e.g. redactive.example.com), the port that will be used for SSL (9443 default), and the full paths to the domain.crt and domain.key files from step 3 above

   

8. Press save and wait for the server to reload
   You will still be on the non-SSL version of the site when it comes back online, so change the address and port to match what was entered in step 6 above
   Examples:

   https://redactive.example.org:9443/admin

   or

   https://redactive.example.org/admin

   if port 443 was chosen for HTTPS
   If you want to change the port to 443, you can do this:

   

   This will allow you to directly go to REDACTIVE instead of appending the port 9443 as shown in the URL below:

   

   

9. If using a self-signed certificate, the browser will display a warning; tell the browser to ignore the warning and proceed

   

source: WKB-000553