Analysis
Overview
Document and research security requirements for resources. Each resource should have permissions including user, group and permissions. These permissions may themselves become resources.
The results of this task well be used by the change server and other security related tasks.
Permissions include: read access, write access, transformable (can be scaled or not for example)
Task requirements
- Define permissions for resources
- Determine if permissions should be resources themselves
Task result
The result of this task is documentation defining the permissions and how they should be used with resources.
Implementation idea
- If a permission set is a resource, what limits the permissions on the permissions resource?
Related
How to demo
Share the documentation for permissions on resources
Design
(Describe your design here.)
Implementation
(Describe and link the implementation results here (from the wiki or the repository).)
Testing
(Place the testing results here.)
Comments
"permission checks "default permissions, etc" related to resources somehow, user, group, several permissions each resource will have security settings resource locator should respect these permissions at some point maybe user and group should be a resource?