Task3G/User Guide/task3G Access
From Documentation
| Revision as of 05:50, 19 April 2006 Moff (Talk | contribs) ← Previous diff |
Revision as of 05:56, 19 April 2006 Moff (Talk | contribs) (→Capabilities) Next diff → |
||
| Line 18: | Line 18: | ||
| === Capabilities === | === Capabilities === | ||
| - | COSMmanager applications such as task3G ‘interpret’ each one of a user’s roles, to determine what capabilities are granted to the user in that application. | + | COSmanager applications such as task3G ‘interpret’ each one of a user’s roles, to determine what capabilities are granted to the user in that application. |
| Line 28: | Line 28: | ||
| The capabilities associated with roles in task3G can be viewed and modified by users with top-level privileges only. Examples of capabilities used within task3G are shown in the table below and the full set can be viewed under task3G configuration > Tables > Roles. | The capabilities associated with roles in task3G can be viewed and modified by users with top-level privileges only. Examples of capabilities used within task3G are shown in the table below and the full set can be viewed under task3G configuration > Tables > Roles. | ||
| - | Capability Description | + | {| border="1" cellpadding="8" cellspacing="0" |
| - | clr_status Ability to manually clear job status | + | !Capability |
| - | control Control task3G jobs and tasks | + | !Description |
| - | disable Ability to disable/enable jobs | + | |- |
| - | display Display contents of task3G tables | + | |clr_status Ability to manually clear job status |
| - | kill Ability to cancel and kill jobs and tasks | + | |- |
| - | killall Ability to kill any task | + | |control |
| - | maintain Maintain task3G tables | + | |Control task3G jobs and tasks |
| - | runall Access to all jobs enabled | + | |- |
| - | submit Ability to submit task3G jobs | + | |disable |
| + | |Ability to disable/enable jobs | ||
| + | |- | ||
| + | |display | ||
| + | |Display contents of task3G tables | ||
| + | |- | ||
| + | |kill | ||
| + | |Ability to cancel and kill jobs and tasks | ||
| + | |- | ||
| + | |killall | ||
| + | |Ability to kill any task | ||
| + | |- | ||
| + | |maintain | ||
| + | |Maintain task3G tables | ||
| + | |- | ||
| + | |runall | ||
| + | |Access to all jobs enabled | ||
| + | |- | ||
| + | |submit | ||
| + | |Ability to submit task3G jobs | ||
| + | |} | ||
| From this example, users without maintain capability should not be able to maintain | From this example, users without maintain capability should not be able to maintain | ||
| Line 43: | Line 63: | ||
| <br> | <br> | ||
| + | |||
| === Steps to Obtaining Access to task3G === | === Steps to Obtaining Access to task3G === | ||
Revision as of 05:56, 19 April 2006
Detailed information on accessing COSMmanager applications can be found in the section COSMmanager Users and Access Controls of the COSMmanager User Guide. The information in this chapter is a summary of the relevant details from that manual.
To access COSMmanager, a user must first have a UNIX account on the same host as COSMmanager, or on a networked host. To actually run any COSMmanager applications, users must have access rights to the required COSMmanager menus and options.
Roles
COSMmanager access is controlled by assigning to selected users one or more roles. Roles equate to responsibilities shared by some staff. Each role translates to a set of capabilities that determine users’ access to menus and functions in individual COSMmanager applications.
By grouping users with similar access requirements and responsibilities, you can avoid having to allocate capabilities to individual users and security is enhanced by granting access rights according to job function, rather than to transient individuals.
Task3G is supplied with a set of default roles such as those shown in the diagram below. These roles can be modified to more accurately reflect the needs of an installation.
Figure 4 — Capabilities and roles
Capabilities
COSmanager applications such as task3G ‘interpret’ each one of a user’s roles, to determine what capabilities are granted to the user in that application.
- Note
- By convention, role names use initial capitals (“Admin”) and capabilities do not (“submit“).
The capabilities associated with roles in task3G can be viewed and modified by users with top-level privileges only. Examples of capabilities used within task3G are shown in the table below and the full set can be viewed under task3G configuration > Tables > Roles.
| Capability | Description |
|---|---|
| clr_status Ability to manually clear job status | |
| control | Control task3G jobs and tasks |
| disable | Ability to disable/enable jobs |
| display | Display contents of task3G tables |
| kill | Ability to cancel and kill jobs and tasks |
| killall | Ability to kill any task |
| maintain | Maintain task3G tables |
| runall | Access to all jobs enabled |
| submit | Ability to submit task3G jobs |
From this example, users without maintain capability should not be able to maintain any duty or access task3G configuration.
Steps to Obtaining Access to task3G
- Add user to COSMmanager as either a user or a group.
- Assign appropriate COSMmanager roles to the user, creating new role if required.
- Ensure capabilities assigned to role within task3G are adequate by examining the ‘task3G Access Capabilities and Roles’ table under task3G configuration > Tables > Roles. Amend or add roles as required.