| 4 | | Role-Based Access Control (RBAC) will be used by Orbit to ''control'' each user's ''access'' to Orbit resources based on his or her ''role''. To explain how RBAC will work, first some terminology. An application program or process acting on behalf of a user is referred to as a subject. An object is any resource accessible on a computer system, including peripherals, files, databases, and fields in a database. An operation is an active process invoked by the subject process much like a function call or a method invocation. A ''permission'' or privilege is the authorization to perform some action on the system. In RBAC, a permission involves the authorization to perform a given operation on a given object. |
| | 4 | Role-Based Access Control (RBAC) will be used by Orbit to ''control'' each user's ''access'' to Orbit resources based on his or her ''role''. To explain how RBAC will work, first some terminology. An application program or process acting on behalf of a user is referred to as a ''subject''. An ''object'' is any resource accessible on a computer system, including peripherals, files, databases, and fields in a database. An ''operation'' is an active part of a process invoked by the subject process much like a function call or a method invocation. A ''permission'' or privilege is the authorization to perform some action on the system. In RBAC, a permission involves the authorization to perform a given operation on a given object. The use of roles to control access is based on the observation that there may be thousands of users in a given organization, but there are perhaps only a hundred different roles they act in at any given time to access resources. Users are assigned to one or more roles and each role has defined permissions for operations issued on behalf of a process run by a user acting in that role to access a given object. |
