Impact
The first-class Redis Cluster configuration cannot represent authenticated or TLS deployments. Sentinel cannot represent separate Sentinel/data-node credentials or TLS either, excluding common managed-production configurations.
Evidence
RedisStoreConfig.Cluster accepts only nodes and read policy. connectCluster constructs plaintext unauthenticated RedisURI.Builder.redis(host, port) seed URIs, and there is no public injected cluster-client constructor.
Acceptance criteria
- Support username/password and TLS verification for Cluster.
- Support distinct Sentinel and Redis data-node ACL credentials plus TLS where Lettuce supports them.
- Do not log credentials in topology descriptions or startup failures.
- Add Spring properties, validation, documentation, and real authenticated/TLS topology tests.
- Preserve the one-slot Lua key layout and master-read requirement.
Impact
The first-class Redis Cluster configuration cannot represent authenticated or TLS deployments. Sentinel cannot represent separate Sentinel/data-node credentials or TLS either, excluding common managed-production configurations.
Evidence
RedisStoreConfig.Clusteraccepts only nodes and read policy.connectClusterconstructs plaintext unauthenticatedRedisURI.Builder.redis(host, port)seed URIs, and there is no public injected cluster-client constructor.Acceptance criteria