diff options
| author | YaacovHazan <31382944+YaacovHazan@users.noreply.github.com> | 2021-09-23 08:52:56 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-09-23 08:52:56 +0300 |
| commit | a56d4533b72db8aa147be090c4c1d2bc548b9408 (patch) | |
| tree | 718d3628bcdb7ca5132324af33b841cb0d1aeeec /redis.conf | |
| parent | 14d6abd8e9a928aa920d5009d79e7b8ff2d0d5ba (diff) | |
| download | redis-a56d4533b72db8aa147be090c4c1d2bc548b9408.tar.gz | |
Adding ACL support for modules (#9309)
This commit introduced a new flag to the RM_Call:
'C' - Check if the command can be executed according to the ACLs associated with it.
Also, three new API's added to check if a command, key, or channel can be executed or accessed
by a user, according to the ACLs associated with it.
- RM_ACLCheckCommandPerm
- RM_ACLCheckKeyPerm
- RM_ACLCheckChannelPerm
The user for these API's is a RedisModuleUser object, that for a Module user returned by the RM_CreateModuleUser API, or for a general ACL user can be retrieved by these two new API's:
- RM_GetCurrentUserName - Retrieve the user name of the client connection behind the current context.
- RM_GetModuleUserFromUserName - Get a RedisModuleUser from a user name
As a result of getting a RedisModuleUser from name, it can now also access the general ACL users (not just ones created by the module).
This mean the already existing API RM_SetModuleUserACL(), can be used to change the ACL rules for such users.
Diffstat (limited to 'redis.conf')
0 files changed, 0 insertions, 0 deletions