...
| Info | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
The information provided on this page only applies to the Classic JOC user interface, which is entering retirement:
The JOC Cockpit user interface is a replacement for JOC:
|
- Job Scheduler provides built-in basic user/password authentication:
- The easiest way to generate the encrypted passwords is to use JOE.
- This mechanism does not support more elaborated management of user credentials, e.g. password expiration policies.
- If you want to authenticate users against an LDAP directory, you can set up a web server as a proxy for JOC.
- This grant access to JobScheduler exclusively from the localhost and from the web server (see the element
<allowed_hosts>in scheduler.xml). - If a user wants to access JOC then the address of the proxy server has to be used. Proxy access can be the secured using plugins of the web server (e.g. Apaches LDAP Plugin).
- This grant access to JobScheduler exclusively from the localhost and from the web server (see the element
...