...
The architecture introduced with the JOC Cockpit ensures that users are restricted to only being able to directly access the JOC Cockpit as illustrated in the diagram below. The JOC Cockpit then calls the Web Service which, in turn, has access to the JobScheduler Masters themselves.
...
See the JOC Cockpit - Architecture article for more information.
HTTP / HTTPS Communication
As indicated in the schematic architecture diagram above, communication between the JOC Cockpit, the Web Service and the JobScheduler Masters can be carried out using both HTTP and HTTPS protocols. By default after installation HTTP will be used. However, HTTPS should be implemented by system administrators for all communication steps when the JobScheduler is to be used in sensitive environments. Information about the configuration of the Jetty Web Server delivered with the JOC Cockpit for HTTPS can be found on the Jetty Web Site.
Log In Form
The Remember Me setting in the JOC Cockpit Log In form shown below allows users to prevent misuse of log in information cached by the browser.
...
Separate authorization tokens are used for each communication step between the JOC Cockpit, the Web Service and the JobScheduler Masters and Agents. This means that if an attacker is able to take over and use a token they will only be able to bypass a part of the communication chain. This means that it will be harder for the attacker to remain undetected.
| Status | ||||
|---|---|---|---|---|
|
| Status | ||
|---|---|---|
|
...
- the browser's local storage will not be emptied after a period of time when Remember Me is set and a user does not log in again,
HTTP / HTTPS Communication
As indicated in the schematic architecture diagram above, communication between the JOC Cockpit, the Web Service and the JobScheduler Masters can be carried out using both HTTP and HTTPS protocols. By default after installation HTTP will be used. However, HTTPS should be implemented by system administrators for all communication steps when the JobScheduler is to be used in sensitive environments. Information about the configuration of the Jetty Web Server delivered with the JOC Cockpit for HTTPS can be found on the Jetty Web Site.