-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Epic] Roles, Permissions and Grants #31
Comments
We don't need Roles, Permissions and Grants to manage access to content in the dwyl App for "single player mode", but it becomes immediately relevant once someone wants to share an item with anyone else. Do they want the other person to have read-only access, edit or co-own the item? This are all questions that can be answered/solved by an RBAC system. My plan for today is to do a "deep dive" into RBAC from first principals and make notes on everything so that anyone I don't expect my research/writeup phase to last more than a few hours, but I don't want to treat this superficially because it's a foundational concept that everyone needs crystal clarity on. My intention is to write up an authoritative but still accessible (beginner-friendly) writeup similar to https://github.com/dwyl/learn-json-web-tokens |
@nelsonic Do you have an ETA on this? |
Hi @th0mas, I got sidetracked researching how we can control the 20 doors without needing 20 RPi0s and 20 POE converters. 🔍 dwyl/smart-home-security-system#14 (comment) |
Roles deployed to https://dwylauth.herokuapp.com/roles Background/docs captured: https://github.com/dwyl/auth/blob/master/role-based-access-control.md Closing. ✅ |
On Monday we drew out the basic auth schema (including Roles, Permissions and User_Roles) on the witeboard in the Office together:
This issue/epic is our attempt to capture as much detail as we can so we can implement it.
If you are interested in this challenge, please read: wikipedia.org/wiki/Role-based_access_control
More detail on the roles schema in #27 (comment)
I will be adding it to here shortly ⏳
# Todo
The text was updated successfully, but these errors were encountered: