Introduction

• The JOC Cockpit implements Authentication and Authorization by a combination of Roles and Permissions.
• Permissions are assigned to Roles which are then assigned to User Accounts.

• The JOC Cockpit - Authentication and Authorization article provides an introduction of the Authentication and Authorization mechanisms.

• This article describes the default Roles and Permissions that are delivered with the JOC Cockpit.

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. Consider that the api_user role by default that is not intended to modify any objects but is intended for monitoring purposes, e.g. when used with a system monitor.

• The list with all permissions for use with the shiro.ini file: shiro.ini
• Roles and Permissions Matrix as file: js7_permissions.xlsx