Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 9

changes.mady.by.user Alan Amos

Saved on

compared with

New Version 10

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Screenshots corrected

...

Editing Permissions will also be described later.

...

Initial Configuration

Adding User Accounts and Roles

...

  • Go to the Accounts view and click on the Create Account button at the top right.
  • This will open the following Modal window:
  • Passwords will be saved in a configuration file in plain textAccount 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 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:

Configuration Test

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

 

Show If
groupsos-members

The above screen shows seven default roles that are delivered with the JOC Cockpit are applicable for all JobScheduler Masters as they are delivered in the JOC Cockpit installation archive. In addition, the following configurations have been added:

  • A role jocc_test had been added with potential access to all JobScheduler Masters.
    • Note that if no permissions are specified for this relationship then this configuration will be removed when the current user leaves the Managing Accounts view.
  • Two JobSchedulers Masters have been specified and roles specific to these JobSchedulers configured:
    • An api_test Role has been created whose permissions are restricted to the JobScheduler Master with ID jobscheduler_1.11.

      • This configuration writes the following to the shiro.ini file:

        Code Block
        languagetext
        [roles]
...
api_test = jobscheduler_1.11:sos:products:commands:jobscheduler_master
...
    • The default application_manager Role has been configured prior to being given or losing permissions specifically for the jobscheduler_1.11_cluster.

      • This configuration writes the following to the shiro.ini file:

        Code Block
        languagetext
        [roles]
...
application_manager = ... , \
..................... jobscheduler_1.11_cluster:sos:products:joc_cockpit:jobscheduler_master:view, \
..................... ...

The Permissions View

The Permissions view is accessed by clicking on a Role in the Master view as indicated in the screenshot above.

The Permissions view allows Permissions and Folders to be specified for individual Roles:

  • either restricting the Role to accessing specific Folders within the live folder of the JobScheduler Master.
    • Note that the default setting is that a Role is allowed access to all Folders - however, after a first folder is specified, the Role will only be able to access that one Folder.
  • granting or removing Permissions for the Role.
    • Note that the default Permissions are none and that permissions can be granted and removed.

In the screenshot above the application_manager Role:

  • is only allowed to access the test Folder and all its child folders on the jobscheduler_1.11_cluster.
  • has been given the sos:products:joc_cockpit:jobscheduler_master:view permission for the jobscheduler_1.11_cluster - this is a higher permission than the default sos:products:joc_cockpit:jobscheduler_master:view permission and allows not just the default status but also parameters and the main log for this JobScheduler Master to be viewed.

The above Permissions add the following code to the shiro.ini file:

Code Block
languagetext
[folders]
jobscheduler_1.11_cluster|application_manager = /test/*
jobscheduler_1.11|api_test = /test/*
 

...