Page History

Introduction

Permissions Hierarchy

Permissions are configured hierarchically:

...

• JobScheduler Master IDs and
• Folders within a JobScheduler's live folder.

Using the Manage Accounts view

Getting Started

After installing the JOC Cockpit, log in with the default root:root user name and password.

...

• Accounts: for the configuration of User Accounts. Accounts configured here use shiro name / password Authentication.
  
  • Note that while Shiro authentication is not as secure as, for example, LDAP, it provides a convenient basis for configuring a authorization in a test environment.
  • See the JOC Cockpit - Authentication and Authorization article for more information about shiro Shiro and other methods of authentication that can be used with the JOC Cockpit.
• Masters: for configuring the JobScheduler Masters that can be accessed by a Role
• Permissions: for configuring access to Folders and the Permissions for a Role

These views will be described in the following sections.

The Accounts View

The Accounts view is the view that is opened first when a User user selects the Manage Accounts view and lists all the User Accounts that have been configured along with the Roles they have been allocatedassigned.

The above screenshot shows the default root User Account view which is the only Account that is configured after installation of the JOC Cockpit.

The Create Account button is used to open a modal window to add a new User Account - clicking on the additional option (ellipsis) symbol or the Account name brings the user to the Master Masters view (described below) where the Account Name, Password and Role(s) allocated can be edited.

The Masters View

The main purpose of the Masters view is to allow JobScheduler Master JobSchedulers Roles to be configured. 

When the view is first opened after installation of the JOC Cockpit it will appear as shown in the next screenshot:

...

The above screen shows seven default roles that are delivered provided with the JOC Cockpit. These Roles are intended to help system administrators get a realistic authorization configuration working as quickly as possible and can be modified as required. These roles are valid for all JobScheduler Master Idsinstances in the environment.

Positioning the mouse over a role name blends in two links as shown in the screenshot above:

...

A set of Permissions is configured for each Role in line with ITIL definitions. Each Permissions Set set can be inspected by clicking on the Role name in the Masters view list. An example Permissions Set set is described in the next section.

The Permissions View

The main purpose of the Permissions view is to allow Permissions and Folders to be configured for each Role.

The Screenshot screenshot below shows the default permissions for the administrator Role.

Individual The individual scope of Permissions can be edited and they can be removed from the Role using the pencil and X symbols that are blended in when the user's mouse is moved over a permission.

...

The Folder part of the view is for restricting the Role to accessing particular Folders - and thereby particular Jobs, Job Chains, etc - within a JobScheduler Master's live folder and will be described later.

Editing Permissions will also be described later.

Initial Configuration

Adding User Accounts and Roles

The following example describes the addition of how to add User Accounts to the JOC Cockpit in addition to the default root user account. Each User Account will be allocated assigned one of the default Roles described in the Masters View section above and for simplicity will use the same name as the Role they will be given.

...

• Go to the Accounts view and click on the Create Account button at the top right.
• This will open the following Modal window:
  
• Account Names may not contain spaces.
• Selecting the administrator Role from the list will avoid possible errors from a mistyped role name.
• It will be clear form the functioning of the Roles Selection selection that any number of Roles can be specified for a User Account if required
• Click the Submit Button to save the Account configuration, which will become active in a few seconds.
  • Note that if one of the Accounts should contain a configuration error (such as a blank space in an Account Name), none of the Accounts will be saved to the configuration file.

Once a User Account has been created for each role, the Accounts view would look like:

Account Use

The root User can now be logged out via the Profile Menu and the other User accounts used.

...

Note that as the default administrator Role is granted a limited Permissions Setset, the Main Menu Bar in the JOC Cockpit only contains a link to the Dashboard view as can be seen in the screenshot below. In contrast, the root User Account has links for a further seven views (see the screenshots above).

By default the administrator role Role is granted Permissions for the Manage Accounts view and therefore the configuration of the User Accounts will continue using this Account rather than root.

...