Authentication and Authorization - Permissions for the JOC Cockpit

Scope

• The JOC Cockpit implements authentication and authorization by a number of permissions.
• Permissions can be assigned to roles that then are assigned to users.

• More information about how this can be done is available in the Authentication and Authorization - Configuration article.

Matrix of Roles and Permissions

The document below shows the default roles and permissions delivered with the JOC Cockpit shiro.ini configuration file. System administrators can define and modify roles and permissions as required.

The purpose of each role is explained in the notes at the foot of the matrix. Of particular interest is the api_user role that is not intended to use the JOC Cockpit interface but use the JobScheduler REST Web Services from another application. More information can be found in the Authentication and Authorization - Permissions for the JobScheduler REST Web Services article.

• Permission list for use with shiro.ini: shiro.ini-JOC-Cockpit-permission-list.txt
• Document: joc-role-operation-permission.xlsx

Complete List of Permissions

The following table shows the permissions that can be set to allow an user to access the JOC Cockpit.

Examples

Allow orders to be viewed and executed

sos:products:commands:order:view, \
sos:products:commands:order:execute, \

Allow all order operations except changing and removing orders

sos:products:commands:order, \
-sos:products:commands:order:change, \
-sos:products:commands:order:remove, \

References

• Authentication and Authorization - Configuration
• Authentication and Authorization - Permissions for the JobScheduler REST Web Services