Running Behind a Proxy 6.4.0

When running behind a proxy, the script (detect.sh or detect.ps1) requires proxy details to do a version check on, and/or download the Synopsys Detect .jar file. Synopsys Detect; in other words, the code in the .jar file, requires proxy details to download inspectors and connect to Black Duck.

Providing proxy details to Synopsys Detect

Synopsys Detect looks for proxy details in the properties whose names start with blackduck.proxy, including:

• blackduck.proxy.host (proxy host)

• blackduck.proxy.port (proxy port)

• blackduck.proxy.username (proxy username)

• blackduck.proxy.password (proxy password)

Providing proxy details to detect.sh

The curl commands executed by detect.sh to do a version check on, and/or download the Synopsys Detect .jar file, require additional command line options when run behind a proxy. For more information on curl options, refer to the curl documentation.

To provide additional curl command line options for detect.sh to use when it executes curl, set the environment variable DETECT_CURL_OPTS before running detect.sh. For example:

When using detect.sh to execute Synopsys Detect you must set proxy properties for Synopsys Detect as previously described.

Providing proxy details to detect.ps1

detect.ps1 derives proxy details from environment variables whose names match the Synopsys Detect proxy property names. Configuring detect.ps1 for your proxy involves setting those environment variables before running detect.ps1. For example:

When using detect.ps1 to execute Synopsys Detect, Synopsys Detect also receives the proxy details from these environment variables, so no additional configuration is required for Synopsys Detect.