Configure Proxy Between JFrog Products

In corporate environments all cross-node communication may be routed a through corporate proxy.

In corporate environments all cross-node communication may be routed through a corporate proxy. To accomplish this, use router services to establish:

  • Internal communication between services and their local router within a JPD.
  • Outbound communication through a proxy.

Repeat the following configuration settings in each service's System YAML Configuration File.

The following example assumes the proxy is listening on 1.2.3.4:7777 for HTTP and on 1.2.3.4:8888 for HTTPS.

router:
  proxy:
    # Proxy url for all outgoing http requests
    httpUrl: "http://1.2.3.4:7777"
    # Proxy url for all outgoing https requests
    httpsUrl: "https://1.2.3.4:8888"
    # List of target hosts to communicate with directly, bypassing the proxy.
    # "localhost" will always be added to this list automatically.
    ignoredHosts:
    - "example1.ignored.host"
    - "example2.ignored.host"

Note that:

  • The router automatically adds localhost to the ignored hosts.
  • The example uses the system configuration file, but you can also use the environment variables JF_ROUTER_PROXY_HTTPURL, JF_ROUTER_PROXY_HTTPSURL, and JF_ROUTER_PROXY_IGNOREDHOSTS.
  • The router respects the standard proxy related environment variables (HTTP_PROXY,HTTPS_PROXY,NO_PROXY), but the router's system configuration takes precedence if it is defined.

Configure all other services in a similar way:

  • Services do not use the proxy to call the local router
  • Services use the proxy to connect to external third party services like Artifactory remote repositories.