2.10 SSL Certificates Management Tab

Secure communications requires Retain server to use industry-recognized Certificate Authorities and Self-signed certificates. On upgrading to Retain 23.2, when certificates are expired or become invalid, you are allowed to upload and manage new certificates.

Earlier we supported secure database only with MariaDB and MySQL. Beginning with Retain 23.2, we support secure database with all the supported database types - MariaDB, MySQL, Oracle, PostgreSQL, and MSSQL.

The certificates can be either a lone certificate or a key pair. Each certificate must have a unique name or it will fail to upload. To create a key pair, you need to upload the cert.pem first and then the key.pem and the alias name should be the same for both. If your database type is Oracle DB, upload a single .p12 certificate.

For Example, if you are generating a new self-signed certificate files with 3 certificates, CA certificate - ca.pem, Client certificate - client-cert.pem, and Client key - client-key.pem, thenyou have to create a key pair. First you have to upload/import the client-cert.pem file, give an alias name to the file. Then, upload the client-key.pem file, give the alias name same as the client-cert.pem file and then upload/import ca.pem with a different alias name.