I am experiencing authentication failures when a sentinel connects to master or each other. I followed the instructions at https://redis.io/docs/management/sentinel/ to create a sentinel user.

Command to create a sentinel user: 127.0.0.1:5000> ACL SETUSER sentinel-user ON >user-password -@all +auth +client|getname +client|id +client|setname +command +hello +ping +role +sentinel|get-master-addr-by-name +sentinel|master +sentinel|myid +sentinel|replicas +sentinel|sentinels

My ACL file configuration (incorporating the fix from https://github.com/redis/redis/issues/9772): user sentinel on sanitize-payload user-password resetchannels -@all +auth +client|getname +client|id +client|setname +command +hello +ping +role +sentinel|get-master-addr-by-name +sentinel|master +sentinel|myid +sentinel|replicas +sentinel|sentinels +sentinel|is-master-down-by-addr

Sentinel configuration:

sentinel sentinel-user sentinel
sentinel sentinel-pass user-password

Changing the user to admin works fine with this configuration: user admin on sanitize-payload user-password ~ & +@all

127.0.0.1:26379> acl log
1)  1) "count"
    2) (integer) 4604
    3) "reason"
    4) "command"
    5) "context"
    6) "toplevel"
    7) "object"
    8) "publish"
    9) "username"
   10) "sentinel"
   11) "age-seconds"
   12) "0.018"
   13) "client-info"
   14) "id=8 addr=10.10.10.134:40844 laddr=10.10.10.133:26379 fd=12 name=sentinel-2c20f51b-cmd age=332 idle=0 flags=N db=0 sub=0 psub=0 ssub=0 multi=-1 qbuf=139 qbuf-free=20335 argv-mem=115 multi-mem=0 rbs=1024 rbp=78 obl=0 oll=0 omem=0 tot-mem=22539 events=r cmd=publish user=sentinel redir=-1 resp=2 lib-name= lib-ver="
   15) "entry-id"
   16) (integer) 2
   17) "timestamp-created"
   18) (integer) 1712191534245
   19) "timestamp-last-updated"
   20) (integer) 1712191864170

Comment From: zulander1

I was using confusing the client and sentinel users. so sentinel users should be admin