source-salesforce: Add HTTP/HTTPS proxy support

[Christos Tsiaras (christostsiaras)]

Description
The Salesforce source connector does not support HTTP/HTTPS proxy configuration. In enterprise environments with strict network egress controls, such as those using a corporate forward proxy or a VPC-level outbound proxy, it is currently not possible to route connector traffic through the required proxy. The connector spec exposes no proxy-related fields, and there is no documented workaround for self-managed deployments.

Desired solution
Add optional proxy_host, proxy_port, and optionally proxy_username / proxy_password fields to the connector's configuration spec, allowing users to specify an HTTP/HTTPS proxy through which all outbound requests to the Salesforce REST and Bulk APIs are routed. Alternatively, honour standard HTTP_PROXY / HTTPS_PROXY environment variables if set on the connector container, consistent with how Python's requests library resolves proxy settings by default.

Additional context
This is a common requirement in regulated industries (finance, telco, healthcare) where all outbound traffic must pass through an audited proxy. Other Airbyte connectors for database sources (e.g. Postgres, MySQL) support SSH tunnel configurations as a comparable network-level control. Parity for SaaS API connectors like Salesforce would meaningfully improve enterprise adoptability.
Connector: source-salesforce | Version: 2.7.23

[Airbyte Support Bot (airbyte-support-bot)]

Hi Christos Tsiaras (@christostsiaras), thank you for opening this discussion and for the detailed write-up!

We understand that HTTP/HTTPS proxy support is an important requirement for enterprise environments with strict network egress controls. This is a reasonable feature request — the underlying Salesforce APIs can certainly be accessed through proxies, and Python's requests library natively supports proxy configuration via both explicit parameters and environment variables (HTTP_PROXY/HTTPS_PROXY).

We've escalated this to our internal team for evaluation. They will review the feasibility of adding proxy configuration fields to the connector spec and/or honoring standard proxy environment variables.

In the meantime, depending on your deployment model, you may want to explore:

• For self-managed (Docker/K8s): Setting HTTP_PROXY and HTTPS_PROXY environment variables on the connector container at the orchestration level (e.g., via Kubernetes pod env vars or Docker --env flags). Python's requests library will pick these up automatically, though this is not officially supported or tested for this connector.
• Network-level proxying: Transparent proxy configurations at the infrastructure layer (e.g., Squid, Envoy sidecar) that intercept outbound traffic without requiring connector-level changes.

These are potential workarounds and not officially supported — your mileage may vary.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

[Airbyte Support Bot (airbyte-support-bot)]

This has been escalated to our internal team for investigation: https://github.com/airbytehq/oncall/issues/12853