14 | | The [wiki:Internal/Rbac/OrbitRbacDesign/NistRbacSoftware NIST RBAC Software], [wiki:Internal/Rbac/OrbitRbacDesign/SolarisRbac Solaris RBAC Software], [wiki:Internal/Rbac/OrbitRbacDesign/OasisRbac OASIS RBAC], and [wiki:Internal/Rbac/OrbitRbacDesign/xoRbac xoRBAC] pages cover the four major implementation choices that were identified during [wiki:Internal/Rbac/OrbitRbacDesign/ImplementationResearch Research for Implementation]. The NIST RBAC software was chosen as a starting point for the implementation of ORBIT RBAC support because it is web-oriented, has a server-pull architecture, supports dynamic separation of duty, is Unix-based, and is most likely to be reliable and maintainable. |
| 14 | The [wiki:Internal/Rbac/OrbitRbacDesign/NistRbacSoftware NIST RBAC Software], [wiki:Internal/Rbac/OrbitRbacDesign/SolarisRbac Solaris RBAC Software], [wiki:Internal/Rbac/OrbitRbacDesign/OasisRbac OASIS RBAC], and [wiki:Internal/Rbac/OrbitRbacDesign/xoRbac xoRBAC] pages cover the four major implementation choices that were identified during [wiki:Internal/Rbac/OrbitRbacDesign/ImplementationResearch Research for Implementation]. The NIST RBAC software was chosen as a starting point for the implementation of ORBIT RBAC support because it is web-oriented, has a server-pull architecture, supports dynamic separation of duty, is Unix-based, and is most likely to be reliable and maintainable. It also should be fairly efficient as it is written in C and Perl with one Java module. |