You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
This project uses a static defination to find parent relationship of roles and resources. That way is hard to handle a situation that a role or a resource has a dynamic parents getter.
Currently my solution is using a proxy class to register parent defination rules implicatly. But this way is ugly and broken the Zen of Python.
I have a plan to refactor the role model and resource model, give them a flexible way to use more dynamic rules.
The text was updated successfully, but these errors were encountered:
Can you elaborate on your plan more and maybe give a concrete example? Would such a system be able to handle an implementation of a "wildcard" acls, perhaps?
I'm evaluating this system for my own use and may be able to contribute.
Maybe it would even be worth looking into using an existing RBAC like https://pypi.python.org/pypi/simple-rbac/0.1.1 so this project could focus on the Flask-specific parts. What do you think?
This project uses a static defination to find parent relationship of roles and resources. That way is hard to handle a situation that a role or a resource has a dynamic parents getter.
Currently my solution is using a proxy class to register parent defination rules implicatly. But this way is ugly and broken the Zen of Python.
I have a plan to refactor the role model and resource model, give them a flexible way to use more dynamic rules.
The text was updated successfully, but these errors were encountered: