Changes between Version 159 and Version 160 of Internal/Rbac/OrbitRbacDesign


Ignore:
Timestamp:
Sep 29, 2006, 3:06:56 PM (18 years ago)
Author:
anonymous
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/Rbac/OrbitRbacDesign

    v159 v160  
    44Siswati 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.
    55=== Design Issues ===
    6 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.Š
     6Role-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.
    77
    88In  [[http://orbit-lab.org/attachment/wiki/Internal/Rbac/RbacResources/i01-kluwer01-jpark.pdf PAS01]] Park, Ahn and Sandhu write "Park and Sandhu identify and describe two different approaches for obtaining a user's attributes on the Web: user-pull and server-pull architectures [[http://orbit-lab.org/attachment/wiki/Internal/Rbac/RbacResources/smart-certificates-extending-x-1.pdf PS99b]] .  They classify these architectures based on "Who pulls the user's attributes?"  In the user-pull architecture, the user pulls her attributes from the attribute server then presents them to the Web servers, which use those attributes for their purposes.  In the server-pull architecture, each Web server pulls user's attributes from the attribute server as needed and uses them for its purposes."  LDAP may be used in either approach [[http://orbit-lab.org/attachment/wiki/Internal/Rbac/RbacResources/i01-kluwer01-jpark.pdf PAS01]].