Hello,
Currently, Redis supports setting an instance-wide password through the "requirepass" directive. Once provided, this password gives free access to all databases in the Redis instance. Would it sound reasonable to have, in the future, a similar way to restrict access to databases themselves? This is not trivial at all since it would probably impact features such as master-slave replication, the flushall and select commands and notifications too. However, it would bring the advantage of easily providing private keyspaces (typically for mutualized environments, where a single instance would be shared between several customers) without having to manage separate redis-servers processes (with each of them listening on a different socket, having different PID and data files, etc.).
Comment From: yossigo
This use case is best addressed by ACLs, introduced in Redis 6. That said, letting different customers share the same redis-server process is probably not a good idea for many other reasons.
Closing this as it's a really old issue, please feel free to re-open if necessary.