Certificates
An overview of certificates in Redis Enterprise Software.
| Redis Enterprise Software |
|---|
Redis Enterprise Software uses self-signed certificates by default to ensure that the product is secure. These certificates are autogenerated on the first node of each Redis Enterprise Software installation and are copied to all other nodes added to the cluster.
You can replace a self-signed certificate with one signed by a certificate authority of your choice.
Supported certificates
Here's the list of supported certificates that create secure, encrypted connections to your Redis Enterprise Software cluster:
| Certificate name | Autogenerated | Description |
|---|---|---|
api |
✅ | Encrypts REST API requests and responses. |
cm |
✅ | Secures connections to the Redis Enterprise Cluster Manager UI. |
ldap_client |
❌ | Secures connections between LDAP clients and LDAP servers. |
metrics_exporter |
✅ | Sends Redis Enterprise metrics to external monitoring tools over a secure connection. |
mtls_trusted_ca |
❌ | Required to enable certificate-based authentication for secure, passwordless access to the REST API. |
proxy |
✅ | Creates secure, encrypted connections between clients and databases. |
syncer |
✅ | For Active-Active or Replica Of databases, encrypts data during the synchronization of participating clusters. |
Certificates that are not autogenerated are optional unless you want to use certain features. For example, you must provide your own ldap_client certificate to enable LDAP authentication or an mtls_trusted_ca certificate to enable certificate-based authentication.
Accept self-signed certificates to access the Cluster Manager UI
When you use the default self-signed certificates and you connect to the Cluster Manager UI over a web browser, you'll see an untrusted connection notification. Depending on your browser, you can allow the connection for each session or add an exception to trust the certificate for all future sessions.