This article describes steps on how to bring their own SSL Certificate for RMM GUI

 

For this example, we assume Customer can generate a fully authenticated/CA issued certificate from their CA server, so they just need a procedure to correctly import the certificate in a way RMM GUI is fully functional.

 

Authenticity or errors with such Customer generated Key/Certificate is NOT Rackware’s responsibility.

 

Background:

RMM has self signed certificate but provides flexibility for Customer to bring in their own authenticated/signed SSL Certificate as well, for the RMM server to work through legitimate SSL certificate when accessing RMM GUI.

 

Symptom:

Occasionally, our self signed certificate may be blocked at Customer site due to either their internal policies and/or AV (such as Bitdefender for example) and RMM GUI may not be fully functional.

 

Before you Begin:

<> 

 

Use case:

  1. Customer wants to use their own SSL Certificate for RMM GUI
  2. RMM’s self signed certificate may be blocked at Customer site due to either their internal policies and/or AV

 

Applicable To:  

ANY RMM version on any installed environment. 

 

Preparation/Pre-Req:

  1. Customer must have ‘root’ access to RMM CLI & ‘admin’ level access to the RMM GUI
  2. Customer must have their own, authentic/signed SSL Key and Certificate

 

Steps:  

  1. We would recommend you to first backup our existing RMM GUI key and certificate file at a safe place to revert if needed.

 

  1. Shut down any open RMM GUI instance/browser

 

  1. The 2 key locations/files on the RMM are as below.  Copy your Certificate and its key at their respective locations on the RMM server, as a ‘root’ user

    /opt/rackware/www/certificates/RackWare_SSL.key
    and
    /opt/rackware/www/certificates/RackWare_SSL.crt

 

  1.  Relaunch a new GUI/browser instance.  This time the new certificate should be operational.

 

 

Post Changes:

<None>

 

Important Note(s):

<None>