You can update the Actor test interface to use a certificate signed by a Certificate Authority (CA). This update helps a proxy, load balancer, or web application firewall (WAF) trust the certificate and allow the traffic to pass through for testing.
- When upgrading Network Actor software, the
https-server-cert.pemandhttps-server-key.pemfiles get overwritten. - As a best practice, back up the
https-server-cert.pemandhttps-server-key.pemfiles before making any changes to the Network Actor software.
- SSH to the Network Actor and switch to the root user:
sudo bash
- Navigate to the folder that contains the test interface certificate:
cd /opt/apps/verodin/node/node/tmp/certs
- Generate a Certificate Signing Request (CSR) with a private key:
openssl req -new -newkey rsa:2048 -nodes -keyout https-server-key.pem -out server.csr
You’re prompted for the CN value, which is generally the FQDN. For example,testint.example.com.FQDNs must comply with RFC 1123, a standard that defines the requirements for FQDNs on the internet. This standard specifies that FQDNs can only contain the following:
- Letters (A-Z, a-z)
- Digits (0-9)
- Hyphens (-)
Underscores are not permitted.
For more information, see RFC 1123: Requirements for Internet Hosts.
- Optional: Check the SSL file
SERVER_KEY_FILENAME.pemand verify consistency:openssl rsa -in SERVER_KEY_FILENAME.pem -check
AnRSA key okresult appears, followed by the output of the key. - Check the CSR, verify the CSR, and and print the data that was entered when generating the CSR:
openssl req -text -noout -verify -in server.csr
- A
verify OKresult appears, followed by the Certificate Request details. - The CA signs the CSR file (
server.csr) with a generated signed certificate.
- A
- Use the CSR to request a certificate from your CA.
- After you receive the certificate from the CA, copy the signed certificate to Network Actor folder:
cp SERVER_CERT_FILENAME.pem /opt/apps/verodin/node/node/tmp/certs
- Rename the signed certificate to
https-server-cert.pem. - Optional: Verify that the certificate and key have matching MD5 has values.
openssl x509 -noout -modulus -in https-server-cert.pem | openssl md5
openssl rsa -noout -modulus -in https-server-key.pem | openssl md5
After these commands are run, two identical MD5 hash values appear. - Restart Network Actor Services:
vrestart
- After generating your signed certificates, export the private key:
openssl pkcs12 -export -out server.p12 -inkey https-server-key.pem -in https-server-cert.pem -certfile <CARoot>.pem