Page History

...

Session Timeout

The JOC Cockpit makes use ofuses the timeout period set in the the shiro.ini configuration file for user sessions:

securityManager.sessionManager.globalSessionTimeout = 900000

The default value of 900'.000 milliseconds translates to 15 minutes. To apply changes to this value the JOC Cockpit has to be restarted.

If a user does not logout from the JOC Cockpit , but e.g. closes the but, for example, closes their browser or browser tab , then:

• the authorization token will remain valid for the specified period since the last user activity.;
• the user session in the JOC Cockpit is closed, however, will be closed but the JobScheduler Web Service will still accept the authorization token for the specified period.

...

The JOC Cockpit ships with a default setting in  the shirothe shiro.ini configuration file for the account "root" to use with the password "root" having permissions for any and with permissions to carry out all operations with the JOC Cockpit.

Please adjust the account and password to be used. For a secure configuration it is recommended to configure that LDAP access to a directory service is implemented for users and with roles with configured in the shiro.ini. This would guarantee that general policies such as frequency of password change or password complexity are considered when using the JOC Cockpit.

See the Authentication and Authorization - Configuration article for more information.

Audit Log

...

A user password cannot be reset or changed with the JOC Cockpit. Depending on the configuration configuration set in the the shiro.ini configuration file :

• users should ask their JobScheduler system administrator to modify the their password in the shiro.ini file if local configuration is used;
• any password changes effected for a directory service are automatically considered when using the JOC Cockpit if LDAP configuration is used.

...