Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
Starting point
- Master and Agent can communicate over HTTPS
- No reverse proxy should be necessarily needed for the communication over HTTPS
Desired Behavior
- Agent accepts HTTPS connections
- New command line to start the Agent: -https-port=<https_port>
- The data directory can also be indicated when starting the agent by the parameter: -data-directory=<DATA>.
Prerequisites
- A Java Keystore has to be generated and stored on the Agent environment. Concretely in the file config/private/private-https.jks
Observations
- A script to generate the Java keystore has been implemented: https://github.com/sos-berlin/scheduler-engine/blob/release/1.10/engine-agent/src/main/resources/com/sos/scheduler/engine/agent/test/generate-self-signed-ssl-certificate-test-keystore.sh
Attachments
Issue Links
- duplicates
-
JS-1589 Agent applies token based authentication for REST web service interface
- Dismissed
-
JS-1592 Agent responds to HTTPS requests with SSL Client Certificate
- Dismissed
- is related to
-
JS-1670 Authentication and HTTPs for JobScheduler Master
- Released
-
SET-68 Agent setup considers HTTPS support and replaced -ip-address option
- Released
- is required by
-
JS-1631 Agent restricts access to authenticated users
- Released
-
JS-1632 JobScheduler Master authenticates itself to Universal Agent
- Released
- requires
-
JS-1633 Agent gets a data directory for configuration and working files
- Released
- mentioned in
-
Page Loading...