...
Connections to Agents are established from Controller instances. If the HTTPS protocol is used then in addition to securing the communication channel the Agent requires mutual authentication.
| Info |
|---|
| title | Keystore, Truststore and Configuration out-of-the-box |
|---|
|
If you are new to certificate management or are looking for a solution that works out of the box then you can use the configuration from the attached archives: - Download
- The archives include the folders:
config.http- This folder includes the
agent.conf configuration file and the private sub-directory with signing certificates. - The contents of this folder corresponds to what you get from the default installation of an Agent.
config.https- This folder includes the
agent.conf configuration file and the private sub-directory with signing certificates and private.conf, keystore and truststore files. - The private key and certificate is created by SOS and works for use with Docker containers that are started for the following hostnames:
js7-agent-primaryjs7-agent-secondaryjs7-controller-primaryjs7-controller-secondary
- As the private key is publicly available you should not consider this a solution to secure your HTTPS connections. However, for evaluation purposes it saves the effort of creating and signing key pairs.
- To apply the configuration replace the contents of the
config folder that is mounted to an Agent container with the contents of the config.http or config.https folders respectively.
|
Agent Keystore and Truststore
...