Logsign Unified SecOps Platform lets you replace the certificate used by the web interface (HTTPS) directly from the UI. You can upload the certificate as a Cer + Key file pair or as a single PFX file.
- Click Settings -> System -> UI Certificates
2. The page has two tabs, one for each way of adding a certificate.
2.1. Upload Certificate: use this tab if you have the certificate and its private key as separate files. Select the certificate with Select Cer File, select the private key with Select Key File, and click Upload. The form has no field for a key passphrase, so the key file must not be password protected.
2.2. Generate Certificate: use this tab if you have a PFX file. Select the file with Select PFX File, enter the PFX password in the Password field (required), and click Generate. Logsign extracts the certificate and the private key from the PFX file.
When the operation succeeds, a Success message is shown and the web server is restarted so the new certificate takes effect. The interface may be unreachable for a few seconds; refresh the browser page afterwards. On a cluster, the certificate is copied to the other nodes and the web server is restarted on them as well.
3. Once a valid certificate is installed, the Upload Certificate tab shows a Certificate Information section with the Subject, Subject Alternative Names, Not Valid Before and Not Valid After values of the active certificate. Use it to confirm that the expected certificate is in use.
Below it, the Notify days before expiry field sets how many days before expiry the system starts warning about the UI certificate. The default is 30 days and the minimum is 15. After changing the value, click the save icon next to the field and confirm. The certificate is also checked by the system health check: it raises a warning when the remaining validity drops to this period, and an error when 5 days or fewer remain or when the certificate has expired or is not valid.