Signing a Wavestore https certificate
When accessing a Wavestore via WaveView or WaveFusion, a self-signed certificate is usually sufficient and no special action is needed. But in some cases, using https from a browser or Onvif Device Manager to access the Wavestore, the certificate should be signed and the relevant root certificate should be imported into client machines. This article describes how to sign the certificate on Wavestore 6.54 and later.
When the Wavestore first runs, it will typically generate a self signed https certificate and also a certificate signing request (CSR). If the IP addresses have changed or if you require a new CSR, execute command new-https-csr. This will leave a csr file in the misc directory called something like https-10.2.3.4.csr. Download this using the File Manager and send it your CA to request that it is signed. These can be signed by any web certification authority (CA). Wavestore Global offer a signing service, there might be a fee for this.
Normally the CSR generated by the Wavestore Server contains one or more IP addresses assigned to that machine. If you need to limit or add IP addresses, or add domain names, see Setting the Subject Alternative Names below
Once the CSR has been generated and downloaded, send it to the CA to be signed.
The CA will sign it (note that there might be a fee for this) and reply with a certificate, usually in a zip file. Load this certificate into the Wavestore using the file manager and run load-https-cert.
The certificate will now be available and new connections from a browser (https) or Onvif client will use it.
If your CA's root certificate is not loaded, you might still see warning messages. Load the Wavestore Global CA Root Certificate if required.
Advanced Options: Setting the Subject Alternative Names
If you need to limit or add IP addresses, or add domain names, you need to explicitly set the Subject Alternative Names (SAN) field in the CSR. This can be done by setting the configuration parameters [SecureLogin] SAN= parameter to a list of IP addresses and DNS names in the format
- IP:<ip-address>
- DNS:<domainname>
separated by commas. There may be any number of these entries. This step is normally not needed as the SAN is usually generated automatically from the list of IP addresses on the machine.
[SecureLogin] SAN=IP:1.2.3.4, IP:2.3.4.6, DNS:wavestore1.mycompany.com
Once this SAN parameter been set in the configuration, execute command new-https-csr again to generate the new CSR.