Keystores for Downloader
You're viewing legacy documentation for API Fortress (deployed via an on-premises container). To view documentation for the new SaaS version of API Fortress — now known as Sauce Labs API Testing and Monitoring (with Sauce Connect tunnels) — see API Testing on the Sauce Labs Cloud.
The downloader (aka:
RemoteDownloadAgent) receives inbound HTTPS connections from the dashboard, encrypting everything with a self-signed certificate.
Here are the steps to install an actual certificate to a RemoteDownloadAgent.
What You'll Need:
Java installed in your systemtip
The Downloader uses a Java Keystore to store the certificate.
- Follow the steps from this Oracle blog post to create a Java Keystore starting from a certificate chain: https://blogs.oracle.com/jtc/installing-trusted-certificates-into-a-java-keystore.
The keystore password must be 450311aa
- Create a derivative image starting from the provided downloader image, which will contain the newly created keystore.
The file needs to be called keystore and must be placed in:
For step 2, an example
Dockerfile may look like the following:
COPY keystore /opt/remoteDownloadAgent/keystore