Configure Halcyon Agent To Communicate Through Proxy – Prod-Sandbox

Applies To

Halcyon Windows Agent version 1.0.2333.1 and higher

Halcyon Linux Agent version 1.0.2333.0 and higher

Overview

With the release of Halcyon Agent version 1.0.2333.x for Windows and Linux, the Agent is now capable of communicating through a proxy to reach Halcyon cloud services. The Agent will attempt a direct connection to the cloud first before falling back to a configured proxy route.

Certificate pinning is still in effect for Halcyon Agents at version 1.0.2333.1 and below, Agent communications must be excluded from SSL inspection.
When specifying the proxy url it is important to correctly specify whether to communicate to the proxy with plain http or with https by specifying the schema, i.e: http://192.168.1.74:3128. If the schema is not specified the agent will assume http.
For Windows Agents, if both ProxyUrl and ProxyPacUrl entries are present, only the ProxyUrl will be used.

Configure Windows Agent

For new Agent installations, you may specify the proxy path either as a direct proxy configuration or an automatic proxy configuration via PAC file at install time.

Direct proxy configuration example:

HalcyonSetup.exe /s /v"/qn" /z"ACCEPTEULA INSTALLTOKEN=%TOKEN% PROXYURL=http://192.168.1.74:3128"

Automatic proxy configuration example:

HalcyonSetup.exe /s /v"/qn" /z"ACCEPTEULA INSTALLTOKEN=%TOKEN% PROXYPACURL=http://192.168.1.74/halcyon.pac"

For currently installed Agents it will be necessary to modify the Halcyon registry key.

If Tamper Guard is enabled for the device, it will be necessary to place the device in maintenance mode and stop the service and driver before attempting to edit the registry.

Direct proxy configuration example:

reg.exe ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Halcyon\Halcyon AR" /v ProxyUrl /t REG_SZ /d "http://192.168.1.74:3128" /f

Automatic proxy configuration example:

reg.exe ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Halcyon\Halcyon AR" /v ProxyPacUrl /t REG_SZ /d "http://192.168.1.74/halcyon.pac" /f

Configure Linux Agent

The Linux Agent does not currently support the use of a PAC file, a direct proxy configuration is the only supported solution at this time. To configure the Linux Agent to use a direct proxy configuration, create or edit file /etc/sysconfig/proxy and add the following details:

PROXY_ENABLED="yes" HTTPS_PROXY="http://192.168.1.74:3128"