> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/engines/install-an-engine/docker/configure-docker-integrations-to-trust-custom-certificates.md). # Configure Docker integrations to trust custom certificates 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, * "/etc/pki/tls/certs", // Fedora/RHEL 2. Restart the engine. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/engines/install-an-engine/docker/configure-docker-integrations-to-trust-custom-certificates.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.