[ https://issues.apache.org/jira/browse/ACE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans updated ACE-279:
---------------------------------
Component/s: Architecture
> Design permissions based on roles
> ---------------------------------
>
> Key: ACE-279
> URL: https://issues.apache.org/jira/browse/ACE-279
> Project: ACE
> Issue Type: Task
> Components: Architecture
> Reporter: Marcel Offermans
> Assignee: Marcel Offermans
>
> On our site we already have a nice page that outlines all the different roles in ACE
(see http://ace.apache.org/dev-doc/requirements/roles.html for more details). What we did
not yet do is map those roles onto different permissions. Our general design for doing this
is described in http://ace.apache.org/dev-doc/design/remote-interfaces.html where the protocol
adapter is also the location where such permissions are handled.
> Per protocol adapter we should make a list of all permissions and map them onto our roles.
That way we end up with a matrix which clearly shows who can do what.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|