jCasbin is an authorization library that supports models like ACL, RBAC, ABAC.
Related to RBAC, casbin has several advantages:
roles can be cascaded, aka roles can have roles.
support resource roles, so users have their roles and resource have their roles too. role = group here.
the permission assignments (or policy in casbin's language) can be persisted in files or database.
multiple models like ACL, BLP, RBAC, ABAC, RESTful are supported.
And you can even customize your own access control model, for example, mix RBAC and ABAC together by using roles and attributes at the same time. It's very flexible.
The security in Presto has to be integrated into the core of the system due to how the query planner and connectors work, so we are not able to outsource this to a third party library.
jCasbin is an authorization library that supports models like ACL, RBAC, ABAC.
Related to RBAC, casbin has several advantages:
And you can even customize your own access control model, for example, mix RBAC and ABAC together by using roles and attributes at the same time. It's very flexible.
I saw there's a RBAC roadmap here: https://github.com/prestodb/presto/issues/10368, and I think jCasbin is a good choice. What do you think? Thanks.