How to Configure Custom HTTPS Certificates on SafeLine WAF

Look at the final result first

Some Idle Talk

The SafeLine Management Platform uses a self-signed certificate by default, which requires an extra click every time you visit, making it a bit inconvenient. So I checked the official documentation but found no relevant information, so I start exploring on my own.

Preparations

Prepare a trusted certificate and private key file in advance.

Steps

1. Connect to the server and locate the /data/safeline/resources/management/certs directory. Back up the default certificates:
   

   mv server.crt server.crt-2023-08-11
   mv server.key server.key-2023-08-11
   

1. Replace the certificates by renaming the trusted certificate and private key to server.crt and server.key, respectively.

1. After replacing, restart the SafeLin service. Since I wasn't sure which specific Docker container it was, I restarted all the SafeLine Docker containers.

Verify the Effect

After the restart, accessing the SafeLine WAF management interface in the browser will show the trusted certificate.