Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 'Rights' deleted

...

The JobScheduler/ JOC Cockpit architecture allows individual JobScheduler Masters and/or Agents to be used for individual clients, and is described in JOC Cockpit - Architecture article. The authentication and authorization introduced with the JOC Cockpit also allows an extremely flexible set of permissions to be configured for Users. Users are allocated one or more roles, with each role containing a set of permissions that specify the operations that can be carried out within the role. In addition, the objects within a JobScheduler Master configuration that these operations can be carried out on can also be configured for each role. For example, one role may be allowed to view the status of Jobs and Orders in Folders A and B, another role may be allowed to change the state and modify the run times of the Jobs and Orders in all the Folders. This approach may be contrasted with other systems that allocate rights and permissions purely according to resources such as files or folders.

The use of role-based rights and permissions brings a number of significant advantages:

  • It simplifies their administration in complex environments. Whilst the administration of the permissions of several hundred folders in a multi-client system is manageable, the administration of several thousand requires brings an extremely high administrative requirement and error susceptibility.
  • Role-based permissions allow the rights and permissions for individual clients to be managed separately.
  • The clear separation of rights and permissions also simplifies meeting compliance requirements.

...