search

hackpar / redis

Automatically exported from code.google.com/p/redis
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

[Feature Request] User Permissions #454

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Is it possible to add permission control feature?
For example: grant RPOP/LPOP priviledge to key 'KeyA, KeyB' to authorized user 
SomeUserA. Any other attempt will be denied.
Or auth with login/pass to list of databases with full access(UserA can access 
databases 3,4,5; UserB can access databases 13, 14, 15).
It'll give ability to maintain various data structures and protect some parts 
of it from different clients in real(far from ideal) production environments.

Original issue reported on code.google.com by rufusepr...@gmail.com on 14 Feb 2011 at 12:54

GoogleCodeExporter commented 8 years ago 
This will not be added, because it goes beyond the scope of Redis. You can add 
such a thing by adding a proxy in front of Redis to check ACLs and so forth. 
That way, you can tailor a solution to your exact needs at the cost of one more 
hop per query.

Original comment by pcnoordh...@gmail.com on 7 Mar 2011 at 11:37

GoogleCodeExporter commented 8 years ago 
this can become a part of webdis, if it isn't already. and actually using a 
separate redis to manage ACLs for key patterns is a cool idea :)

Original comment by dvir...@gmail.com on 7 Mar 2011 at 12:45

GoogleCodeExporter commented 8 years ago 
Webdis already has ACLs, matching users on IP + mask and/or HTTP Basic Auth.

Original comment by n.favref...@gmail.com on 7 Mar 2011 at 1:11

GoogleCodeExporter commented 8 years ago 
I actually implemented proxy in python to meet my auth needs. Overhead is one 
hop per request and it's not a big deal to me.
https://github.com/dredozubov/rpac

Original comment by rufusepr...@gmail.com on 13 Mar 2011 at 7:03