Back to results for “Security & Authentication”
Redis › TLS & Encryption in Redis

How does mutual TLS authentication differ from standard one way TLS, and why would you enable it for Redis?

Intermediate

Answer

Standard TLS only verifies the identity of the server to the client, while mutual TLS additionally requires the client to present its own valid certificate, which the server verifies before allowing the connection, giving you strong assurance that only trusted, known clients can connect to Redis even if someone gains network access to the Redis port.
redis-server --tls-port 6379 --tls-auth-clients yes \
  --tls-cert-file redis.crt --tls-key-file redis.key \
  --tls-ca-cert-file ca.crt
Real-world example A healthcare platform requires every application server connecting to its Redis cluster to present a valid client certificate, ensuring that only explicitly authorized services can access sensitive patient session data.

Common follow-ups: What happens if a client connects without a valid certificate when mutual TLS is required?;How does mutual TLS interact with Redis ACL based authentication?