Changes between Version 149 and Version 150 of Internal/Rbac/OrbitRbacDesign

Timestamp:

Sep 20, 2006, 5:15:59 PM (18 years ago)

Author:

hedinger

Comment:

—

Internal/Rbac/OrbitRbacDesign

@@ -2 +2 @@
 == ORBIT RBAC Design ==
 === Previous Work ===
-Siswati Swami's recent "Requirements Specifications for ORBIT Access Control" [[http://orbit-lab.org/attachment/wiki/Internal/Rbac/RbacResources/Specs2.pdf Swa06]] contains an analysis of each of the roles in which an ORBIT user might act when working on an ORBIT project.  The analysis is based on use cases [[http://orbit-lab.org/attachment/wiki/Internal/Rbac/RbacResources/IC_TECH_REPORT_200131.pdf NW01]] and  [[http://orbit-lab.org/attachment/wiki/Internal/Rbac/RbacResources/fernandez97determining.pdf FH97]], and the specification contains a permissions matrix with access granted or not granted for each role and resource combination.
+Siswati Swami's recent "Requirements Specifications for ORBIT Access Control" [[http://orbit-lab.org/attachment/wiki/Internal/Rbac/RbacResources/Specs2.pdf Swa06]] contains an analysis of each of the roles in which an ORBIT user might act when working on an ORBIT project.  The analysis is based on use cases [[http://orbit-lab.org/attachment/wiki/Internal/Rbac/RbacResources/IC_TECH_REPORT_200131.pdf NW01]] and  [[http://orbit-lab.org/attachment/wiki/Internal/Rbac/RbacResources/fernandez97determining.pdf FH97]].  The specification contains a permissions matrix with access granted or not granted for each role and resource combination.
 === Design Issues ===
 Role-based access control for ORBIT has to allow roles to be expressed in a project context.  That is, a specific project would be constraint on Project Leader and Project Member roles for example.  The primary resources are project-owned data.