| Table of Contents |
|---|
| outlinh1. true |
|---|
| outlinh1. true |
|---|
| 1 | printablefalse |
|---|
| 2 | stylh1. none |
|---|
| 3 | indent20px |
|---|
|
JobScheduler provides a lot of possibilities to secure the access via JOC.
| Info |
|---|
| title | This article only applies to the Classic JOC Interface |
|---|
|
The Classic JOC user interface is entering retirement: | Display feature availability |
|---|
|
The JOC Cockpit user interface is a replacement for the Classic JOC interface: | Display feature availability |
|---|
|
See the JOC Cockpit - Authentication and Authorization Article for more information about configuring the security of the JOC Cockpit. |
JobScheduler provides multiple possibilities to secure access to JOC.
- JobScheduler can be configured with security settings for different hosts that would allow access to JOCThe simplest form is to configure JobScheduler with different security settings for different server (see JOC with restricted permissions and How to determine the for details).Since
- JobScheduler has implemented the jetty webserver it is possible to use different security settings based on the user logged in (see user authentication with jetty for details).comes with the Jetty web server and can be configured for user authentication
- Operate JOC with an Apache Proxy, see How to operate JOC with Last but not least a lot of customers runs JOC behind an Apache Proxy.