- With the CLI
- Without the CLI
If you start the agent with
infisical agent-vault run, the CLI sets up trust for you. On every run, it fetches the certificate from the proxy and sets these variables for the agent: SSL_CERT_FILE, NODE_EXTRA_CA_CERTS, REQUESTS_CA_BUNDLE, CURL_CA_BUNDLE, GIT_SSL_CAINFO, and DENO_CERT.On macOS, if you run the CLI in a terminal, it also adds the certificate to your login keychain for tools such as gh and docker that read the system trust store. macOS asks you to approve the change. To skip this step on a machine that already trusts the proxy, pass --no-ca-trust.Download the certificate authority
To give the proxy’s CA to a sandbox provider, or to get the CA without connecting to the proxy, download it from Infisical:- In Infisical: on the Proxies page of your Agent Vault project, select the download icon next to the fingerprint in the Certificate Authority column
- With the API: call the Get proxy certificate authority endpoint as a member or admin of the proxy’s Agent Vault project
Pin the proxy’s certificate
If the agent runs on a network you don’t fully control, pin the proxy’s certificate so the agent only talks to your proxy. Copy the fingerprint from the Certificate Authority column on the Proxies page:
--ca-fingerprint:
Use your own certificate authority
If your agents’ machines already trust a CA that your organization runs, the proxy can serve that CA, so you don’t have to set up trust for the one Infisical generates. To serve your own CA instead of the one Infisical generates, pass it to the proxy with--ca-cert and --ca-key, or with the INFISICAL_AGENT_VAULT_CA_CERT and INFISICAL_AGENT_VAULT_CA_KEY environment variables. Each value can be the PEM text, the PEM encoded as base64, or the path to a PEM file. The key has to be an ECDSA P-256 key.