gresrun/jesque — Issue #10: AUTH issue with Redis 2.4.0+
Author: ruckus
Created: 2011-10-17 22:01:19+00:00
State: open

I am trying to upgrade to Redis 2.4.0 (saw same issue in 2.4.1) and am using the Jedis 2.0.0.

My redis config is NOT using authentication yet on startup I receive this exception:

```
redis.clients.jedis.exceptions.JedisDataException: ERR Client sent AUTH, but no password is set
at redis.clients.jedis.Protocol.processError(Protocol.java:55)
at redis.clients.jedis.Protocol.process(Protocol.java:62)
at redis.clients.jedis.Protocol.read(Protocol.java:127)
at redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:162)
at redis.clients.jedis.BinaryClient.connect(BinaryClient.java:58)
at redis.clients.jedis.Connection.sendCommand(Connection.java:80)
at redis.clients.jedis.Connection.sendCommand(Connection.java:76)
at redis.clients.jedis.BinaryClient.auth(BinaryClient.java:468)
at redis.clients.jedis.Jedis.auth(Jedis.java:1966)
```

If I build the latest Jedis from trunk (`jedis-2.0.1-SNAPSHOT.jar`) I get the same error.

Downgrading to Redis 2.2.14 solves the problem. Is there anything I can do on my end so we can continue to push out Redis 2.4?

Thanks.