Issues with ACL rules for Sentinel

[Ankit Gupta]

I am following #ACL rules for Sentinel and Replicas described in https://redis.io/docs/management/security/acl/
but getting below exception while running the command as-is.

127.0.0.1:26379> ACL SETUSER sentinel-user on >somepassword allchannels +multi +slaveof +ping +exec +subscribe +config|rewrite +role +publish +info +client|setname +client|kill +script|kill
(error) ERR Error in ACL SETUSER modifier '+multi': Unknown command or category name in ACL
127.0.0.1:26379>

In which use-cases will acl on sentinel will be helpful ?

Looking for a prompt response on this. Thanks in advance.

[Itamar Haber]

Hello Ankit,

The error suggests that you're configuring the ACL of the Sentinel instance (as `MULTI` is a Redis command, not Sentinels).

The use case for Sentinel's ACL is the same as any ACL - control of access to the resource. For example, you may want the application to be able to discover the active Redis masters but block it from performing configuration changes. This, and much more, can be accomplished with Sentinel's ACLs.

Cheers,

Itamar

[Ankit Gupta]

Thanks for the prompt response Itamer :)

Got confused as we were setting up sentinel-user.