Redis Sentinel Cache Backend and authentication

[sushiMix]

Hello, i'm using superset 6.0.1 and I have :

• sentinel without authentication
• redis nodes with authentication (specific user/password).

I'm struggling with configuration which always fails with "No slave found"

It looks like the configuration of RedisSentinelCacheBackend does not support usage of redis username whereas RedisCacheBackend has

superset/superset/async_events/cache_backend.py

Line 151 in 3dd5e69

if configured_username := config.get("CACHE_REDIS_USER"):

.

Is there a way to configure the username ?
I started from this configuration https://superset.apache.org/admin-docs/configuration/cache#configuration.

[dosubot[bot]]

You're correct — RedisSentinelCacheBackend does not support the username parameter for Redis 6+ ACL authentication, whereas RedisCacheBackend does (via CACHE_REDIS_USER) [1]. The Sentinel backend only accepts password and sentinel_password, with no way to pass a username to the underlying Redis nodes [2]. This is a feature gap introduced when the Sentinel backend was added in PR #29912 [3].

The "No slave found" error is likely because Sentinel cannot properly authenticate to discover replicas without the username credential.

Workarounds:

1. Switch to password-only auth — If feasible, configure your Redis nodes to use legacy auth mode (password without username/ACL).
2. Patch the backend locally — You could subclass or modify RedisSentinelCacheBackend to extract a username from config and pass it through master_kwargs to sentinel.master_for() and sentinel.slave_for(), similar to how RedisCacheBackend handles it [1].

This looks like a valid feature request — adding username support to RedisSentinelCacheBackend for parity with RedisCacheBackend would be a relatively small change if you'd like to submit a PR.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[sushiMix]

@dosu can you convert this discussion to a feature request ?

[dosubot[bot]]

I'm not able to convert discussions to issues or change their category on GitHub — I don't have permissions to modify repository settings or issue tracking.

You can convert this discussion to an issue yourself by clicking the "Create issue from discussion" option in the sidebar on the right side of this discussion page (under the ⚙️ gear icon). Alternatively, you could create a new issue and reference this discussion in it.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.