| Info |
|---|
| title | This article only applies to the Classic JOC user interface |
|---|
|
The Classic JOC user interface is entering retirement: | Display feature availability |
|---|
|
The JOC Cockpit user interface replaces the Classic JOC interface: | Display feature availability |
|---|
|
See the JOC Cockpit - Authentication and Authorization Article for more information. |
| Table of Contents |
|---|
| outlinh1. true |
|---|
| outlinh1. true |
|---|
| 1 | printablefalse |
|---|
| 2 | stylh1. none |
|---|
| 3 | indent20px |
|---|
|
Scope
There are three options to enable HTTP authentication for JOC:
- Configure ./config/scheduler.xml
- Configure an Apache and use it as a proxy
- Configure the Jetty plugin
Configure ./config/scheduler.xml
...
| Code Block |
|---|
|
...
<http_server>
<http_directory path="${SCHEDULER_DATA}/" url_path="/scheduler_data/"/>
<http_directory path="${SCHEDULER_HOME}/" url_path="/scheduler_home/"/>
<http.authentication>
<http.users>
<http.user name="admin" password_md5="21232F297A57A5A743894A0E4A801FC3"/>
</http.users>
</http.authentication>
</http_server>
...
|
...