Hi, I believe its important to offer TLS options for redis connections, even using Redis Cloud it's mandatory to use it and custom redis servers must have TLS connections.
This screen should have more options, such as enabling TLS and upload/path to ca, certificate, and key files.
I would like to bring an issue regarding Redis connections when using TLS with Node.js in a local development environment.
Issue:
In Redis Cloud services, it is not mandatory to use TLS, which I initially misunderstood. The infrastructure supports both secure and non-secure connections. However, when using a self-hosted Redis server with TLS enabled, "rediss" does not work as expected. This is because it attempts to use a self-signed certificate, and Node.js rejects the connection due to strict certificate validation. Here's what I have observed:
In production (server environment): Using "rediss" works because Node.js connects using the server's domain certificate, allowing TLS to function properly.
In local environments (e.g., Electron or Docker): Node.js tries to use the self-signed certificate, which is rejected because Node.js performs strict certificate verification and validation when TLS is required.
Request:
I suggest adding an option in the Server Connect Settings window to allow custom certificates to be configured. For development environments, it would be helpful to have an option to enable or disable certificate verification with the following configuration:
This would allow better control over Redis connections, especially in local development with self-signed certificates. It would be great to have this option for development targets, while maintaining strict security for production environments.