Configure Docker integrations to trust custom certificates

Configure Docker integrations to trust custom certificates in Cortex XSOAR 8.10 On-prem.

Python, Javascript, and native integrations running in Docker use an engine's built-in set of CA-signed certificates to validate TLS communication. If you need to change the certificate bundle of the operating system you are working on, for Javascript and native integrations you need to add custom trusted certificates to the engine built-in set, and for Python Docker integrations you need to create a certificate file that includes the custom certificates and add it to the engine. This is relevant for example if you work with a proxy that performs SSL traffic inspection or use a service that has a self-signed certificate.

Configure Javascript and Native integrations to trust custom certificates

1. Add the certificate to the machine’s trusted root CA bundle. The location of the CA bundle depends on the operating system version and the operating configuration.

   Examples of bundle paths:

   • "/etc/ssl/certs/ca-certificates.crt", // Debian/Ubuntu/Gentoo etc.

   • "/etc/pki/tls/certs/ca-bundle.crt", // Fedora/RHEL 6

   • "/etc/ssl/ca-bundle.pem", // OpenSUSE

   • "/etc/pki/tls/cacert.pem", // OpenELEC

   • "/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem", //RHEL 7

   • "/etc/ssl/cert.pem", // Alpine Linux

   Examples of certificate bundle directories:

   • "/etc/ssl/certs", // SLES10/SLES11, https://golang.org/issue/12139

   • "/etc/pki/tls/certs", // Fedora/RHEL

2. Restart the engine.