Introduction

• The JOC Cockpit implements Authentication and Authorization by a combination of JS7 - Identity Services implement JS7 - Authentication and JS7 - Authorization by Roles and Permissions.
• Permissions are assigned to Roles which that are then in turn 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 CockpitJS7 ships by default with a number of Roles and Permissions that can be modified as required, see the JS7 - Manage Roles and Permissions article for more information.

Matrix of Default Roles and Permissions

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

The purpose of each role is explained in with the notes at the foot of the matrix. Consider Note that the api_user role user role by default that is not intended to modify any objects but is intended for monitoring purposes, e.g. for example, when used with a system monitorSystem Monitor.

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