Page History

...

1. Table of User Names and Passwords (SOS_USER) - Structure

   	COLUMN_NAME	DATA_TYPE	NULLABLE	DATA_DEFAULT	COLUMN_ID	COMMENTS
   1	ID	NUMBER(9,0)	No	(null)	1	(null)
   2	SOS_USER_NAME	VARCHAR2(250 BYTE)	Yes	(null)	2	(null)
   3	SOS_USER_PASSWORD	VARCHAR2(250 BYTE)	Yes	(null)	3	(null)

   
   Table of User Names and Passwords (SOS_USER) - Contents

   	ID	SOS_USER_NAME	SOS_USER_PASSWORD
   1	1	administrator	secret
   2	2	application_manager	secret
   3	3	it_operator	secret
   4	4	incident_manager	secret
   5	5	business_user	secret
   6	6	api_user	secret
   7	7	root	root

   
   
   

2. Table of Roles (SOS_USER_ROLE) - Structure

   COLUMN_NAME	DATA_TYPE	NULLABLE	DATA_DEFAULT	COLUMN_ID	COMMENTS
   ID	NUMBER(9,0)	No	(null)	1	(null)
   SOS_USER_ROLE	VARCHAR2(250 BYTE)	Yes	(null)	2	(null)

    

   Table of Roles (SOS_USER_ROLE) - Contents

   ID	SOS_USER_ROLE
   1	administrator
   2	application_manager
   3	it_operator
   4	incident_manager
   5	business_user
   6	api_user
   7	all

   
   
   

3. Table Mapping Roles to Permissions (SOS_USER_PERMISSION) - Structure

   COLUMN_NAME	DATA_TYPE	NULLABLE	DATA_DEFAULT	COLUMN_ID	COMMENTS
   ID	NUMBER(9,0)	No	(null)	1	(null)
   ROLE_ID	NUMBER(9,0)	Yes	(null)	2	(null)
   USER_ID	NUMBER(9,0)	Yes	(null)	3	(null)
   SOS_USER_ROLE	VARCHAR2(250 BYTE)	Yes	(null)	4	(null)

4. Table Mapping Roles to Permissions (SOS_USER_PERMISSION) - Contents

   ID	ROLE_ID	USER_ID	SOS_USER_PERMISSION
   1	1	7	(null)
   2	2	1	(null)
   3	1	(null)	sos:products
   4	2	(null)	sos:products:joc_cockpit:jobscheduler_master:view
   5	2	(null)	sos:products:joc_cockpit:jobscheduler_master:pause
   6	2	(null)	sos:products:joc_cockpit:jobscheduler_master:continue
   7	2	(null)	sos:products:joc_cockpit:jobscheduler_master:restart
   8	2	(null)	sos:products:joc_cockpit:jobscheduler_master:terminate
   9	2	(null)	sos:products:joc_cockpit:jobscheduler_master:abort
   10	2	(null)	sos:products:joc_cockpit:jobscheduler_master_cluster
   11	2	(null)	sos:products:joc_cockpit:jobscheduler_universal_agent

   Shown are the default permissions for user root (ID=7) mapped to role all (ID=1) and user administrator (ID=1) mapped to role administrator (ID=2).

[folders] Configuration

This feature is available from the following issues:

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-137

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-155

System Administrators can add a [folders] section to the shiro.ini file to define the folders that can be accessed by a role within the live folder of a JobScheduler configuration.

...

• For detailed information about the complete permission set see 
  • Authentication and Authorization - Permissions for the JOC Cockpit Web Service
  • Authentication and Authorization - Permissions for the JobScheduler REST Web Service

...

scheduler_id2|my_role=/abcd,