summaryrefslogtreecommitdiff
path: root/sentinel.conf
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2020-03-16 17:11:43 +0100
committerantirez <antirez@gmail.com>2020-03-16 17:11:43 +0100
commitb3a97004f4c5555158f774279e5e2131cf909a6d (patch)
tree7175b1a9cdf0a399aaf8b1a4ad991069c3b296eb /sentinel.conf
parent29b9d0a245135a0b9e024032a7cccd2c238103a9 (diff)
downloadredis-b3a97004f4c5555158f774279e5e2131cf909a6d.tar.gz
Sentinel: document auth-user directive.
Diffstat (limited to 'sentinel.conf')
-rw-r--r--sentinel.conf12
1 files changed, 12 insertions, 0 deletions
diff --git a/sentinel.conf b/sentinel.conf
index 796f45088..4ca5e5f8f 100644
--- a/sentinel.conf
+++ b/sentinel.conf
@@ -102,6 +102,18 @@ sentinel monitor mymaster 127.0.0.1 6379 2
#
# sentinel auth-pass mymaster MySUPER--secret-0123passw0rd
+# sentinel auth-user <master-name> <username>
+#
+# This is useful in order to authenticate to instances having ACL capabilities,
+# that is, running Redis 6.0 or greater. When just auth-pass is provided the
+# Sentinel instance will authenticate to Redis using the old "AUTH <pass>"
+# method. When also an username is provided, it will use "AUTH <user> <pass>".
+# In the Redis servers side, the ACL to provide just minimal access to
+# Sentinel instances, should be configured along the following lines:
+#
+# user sentinel-user >somepassword +client +subscribe +publish \
+# +ping +info +multi +slaveof +config +client +exec on
+
# sentinel down-after-milliseconds <master-name> <milliseconds>
#
# Number of milliseconds the master (or any attached replica or sentinel) should