...
Adding Permissions:
- The Add Permission button in the Permissions View allows a Permission to be selected from a list of all available Permissions as shown in the screenshot below.
- Note that the Permissions listed are all individual Permissions. They can be edited to make them higher level / less specific.
- For example, the screenshot below shows that the
...jobscheduler_master:execute:restart:terminate
permission in the process being selected. - Once selected the Permission can be edited before the Submit button is clicked. This allows, for example, the Permission to be modified to
...
, allowing the Role to carry out all operations covered by this Permission. These are:jobscheduler
_master:execute:restart
sos:products:joccockpit:
jobscheduler
_master:execute:restart:terminatesos:products:joccockpit:
jobscheduler
_master:execute:restart:abort
- The following screenshot shows the edited version alongside the original:
- A selected permission can also be made subtractive - i.e. to remove a specific part of a higher level Permission.
- This is done by ticking the Excluded checkbox.
- For example, the screenshot below shows that the
- Note that the Permissions listed are all individual Permissions. They can be edited to make them higher level / less specific.
- The Add Permission button in the Permissions View allows a Permission to be selected from a list of all available Permissions as shown in the screenshot below.
Modifying Existing Permissions:
- The pencil symbol shown alongside existing Permissions in the Permissions view (shown in the screenshot above) can be used to change the function of a Permission in a Role - to make an additive Permission subtractive and vice-versa. It cannot be used to edit a Permission.
- The X symbol shown alongside existing Permissions in the Permissions view can be used to remove an existing Permission from a Role.
Graphical Permissions Editing:
- The Graphical Permissions Editor is activated by selecting the 'Tree' symbol at the top right of the Permissions section.
- The editor opens with a partially collapsed permissions tree as shown in the next screenshot:
- The Expand tree button (shown in the above screenshot) can be used to open all the tree elements.
Navigation is carried out by dragging & dropping the tree view.
The functions available for the tree elements are (with reference to the screenshot below):
- Select / Unselect a Permission - click on the body of an unselected / selected element
- Selected Permission elements are shown in blue (see the view element in the screenshot)
- Children of selected Permission elements are shown in light blue (as shown in the screenshot)
- Negate a Permission - click on the plus sign at the left hand end of the element
- Remove a Permission Negation - click on a - sign at the left hand end of the element
- Show / hide child elements - click on the + / - symbols at the right hand end of an element
- Select / Unselect a Permission - click on the body of an unselected / selected element
In the following screenshot the view element has been selected, automatically selecting the view:status, view:parameter and view:mainlog child permissions.
In addition, the view:mainlog child permission has been negated, meaning that only the view:status and view:parameter child permissions are active.
- The Graphical Permissions Editor is activated by selecting the 'Tree' symbol at the top right of the Permissions section.
JobScheduler-Specific Permissions
By default User Accounts are granted Permissions for all the JobScheduler Masters and JobScheduler Master Clusters in a scheduling environment - the default Master in the Managing Accounts view. However,
...
Permissions that are only
...
applicable to a particular JobScheduler Master or JobScheduler Master Cluster can be specified for a Role. This is done in the Masters
...
tab of the Manage Accounts view as shown in the next screenshot.
...
In the screenshot the demo_role Role has been assigned for the Master with the ID jobscheduler_1.11. and will appear in the Masters view as shown.
In this configuration the demo_role will not yet have any Permissions that are specific to the jobscheduler_1.11. At least one Permission needs to be added before the jobscheduler_1.11 - demo_role configuration will be permanently saved.
The interaction of default and Master-specific Permissions within the same Role can be illustrated as follows.
- default Permissions:
sos:products:joc_cockpit:jobscheduler_master:view
sos:products:joc_cockpit:jobscheduler_master_cluster:view
- Master-specific Permissions:
sos:products:joc_cockpit:jobscheduler_universal_agent:view
The dashboard view for all JobScheduler Masters in the environment will show the status of the current JobScheduler Master Cluster but the status of Agent Clusters will only be shown for the specified Master - in this case jobscheduler_1.11.
Anchor | ||||
---|---|---|---|---|
|
...