Connecting to a sentinel Redis 5.0.1 server fails with `NOAUTH Authentication required`

Expected behavior

I should be able to connect to a sentinel node of Redis 5.

Actual behavior

I am trying to connect to the sentinel node of a Redis setup in AWS, and I am getting the message:

NOAUTH Authentication required.

Steps to reproduce or test case

Redis version

5.0.1

Redisson version

3.10.4

Redisson configuration

Config config = new Config();
SentinelServersConfig sentinelConfig = config.useSentinelServers();
sentinelConfig.setPassword("**************");
sentinelConfig
                .setMasterName("redis-master")
                .addSentinelAddress("redis://redis-sentinel");

RedissonClient client = Redisson.create(config);

[mranest]

Hello, just found this issue due to a regression in the behaviour of my app. In my case a password is set for Redis master/slaves, and no auth is set for sentinels, as I am running Redis 4. I am also using spring boot, and setting up Redis connection factories et al through redisson-spring-boot-starter. Right now there is no way to configure the app to start when Redis 4 is being used and master/slaves are configured with password. I believe the change where a password set is copied for both master/slaves and sentinels should be reverted, and re-introduced after the resolution of #81. The initialization process as it stands right now is only feasible with Redis 5 and the same password shared between all of Redis types.

Please note that the RedisProperties configuration class of spring boot is also used for Jedis and Lettuce initialization, and neither make use of the password as is currently coded in 3.10.6 (i.e. a non authenticated sentinel is assumed).

Will revert to 3.10.4 for now.

[mranest]

@mranest

Fixed!

Awesome, many thanks! 👍