-
Notifications
You must be signed in to change notification settings - Fork 986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RedisURI class does not parse password when using redis-sentinel #1232
Comments
The password configured via a Please provide a RedisURI redisURI = RedisURI.create("redis-sentinel://password@localhost:26379/0#mymaster");
redisURI.getSentinels().forEach(it -> it.setPassword("my-sentinel-password")); Since the URI format is not flexible enough to represent multiple passwords, especially in the light that Redis 6 is going to ship username and password support, we cannot really do anything useful here. Adding query parameters ( |
no wonder. I was expecting something of the format Because if we look at the documentation for RedisURI , the format specifies the password in the connection string. |
The URI format specifies |
when you say userinfo, what does userinfo exactly mean? So to confirm, for the redis-sentinel connection string, the password@ is actually talking about the redis master password? and not the sentinel instance password ( which is not supported right now ) Also in the connection string it uses the fragment &sentinelMasterId=mymaster , however that does not seem to work, instead i had to use #/mymaster. Is this the correct way? |
Regarding the master Id, bot approaches, the fragment and |
The docs are updated now to reflect the actual behavior. |
@mp911de Shouldn't we reconsider returning to this issue and address that as an enhancement? |
Bug Report
If our redis sentinel setup has password setup on the sentinel instances, providing the connection string of the format 'redis-sentinel://[email protected]:26379/0#mymaster' will cause it to report NOAUTH Authentication required, however if we remove the password setup on the sentinel instances, it will work as expected; that is it directs us to the redis master instance.
Current Behavior
Environment
The text was updated successfully, but these errors were encountered: