summaryrefslogtreecommitdiff
path: root/redis.conf
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2019-02-12 18:23:00 +0100
committerantirez <antirez@gmail.com>2019-02-12 18:23:00 +0100
commitfb7bfc17cdfff18631c5394e1770bb8306634b7a (patch)
tree45be9d9a380aedfe1aa41c1e62fb14d4e29d6407 /redis.conf
parentbfdcfbb3ed906c005c1411ddd4945738da7214c3 (diff)
downloadredis-fb7bfc17cdfff18631c5394e1770bb8306634b7a.tar.gz
ACL: Document masteruser option in redis.conf.
Diffstat (limited to 'redis.conf')
-rw-r--r--redis.conf11
1 files changed, 11 insertions, 0 deletions
diff --git a/redis.conf b/redis.conf
index 71214b620..e4de9ac64 100644
--- a/redis.conf
+++ b/redis.conf
@@ -291,6 +291,17 @@ dir ./
# refuse the replica request.
#
# masterauth <master-password>
+#
+# However this is not enough if you are using Redis ACLs (for Redis version
+# 6 or greater), and the default user is not capable of running the PSYNC
+# command and/or other commands needed for replication. In this case it's
+# better to configure a special user to use with replication, and specify the
+# masteruser configuration as such:
+#
+# masteruser <username>
+#
+# When masteruser is specified, the replica will authenticate against its
+# master using the new AUTH form: AUTH <username> <password>.
# When a replica loses its connection with the master, or when the replication
# is still in progress, the replica can act in two different ways: