For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Open sourceSupportFAQsDocs Home
DocumentationCommand referenceRelease notes
DocumentationCommand referenceRelease notes
  • Itential Automation Gateway
    • Overview
    • Execution engine
    • Concepts
    • Feature comparison
        • Create certificates
        • Initial configuration
        • Configure gateway client
        • Configure client profiles
        • Create cluster in Gateway Manager
        • High availability clusters
        • Distributed execution clusters
          • Overview
          • Application variables
          • Client variables
          • Connect variables
          • Features variables
          • Log variables
          • Registry variables
          • Runner variables
          • Secrets variables
          • Server variables
          • Store variables
          • Terminal variables
      • Migrate inventory to IAG 5
    • IAG secret store
    • Inventory Manager
LogoLogo
Open sourceSupportFAQsDocs Home
On this page
  • GATEWAY_CONNECT_CERTIFICATE_FILE
  • Environment Variable
  • File
  • Default
  • GATEWAY_CONNECT_ENABLED
  • Environment Variable
  • File
  • Default
  • GATEWAY_CONNECT_HOSTS
  • Environment Variable
  • File
  • Default
  • GATEWAY_CONNECT_INSECURE_TLS
  • Environment Variable
  • File
  • Default
  • GATEWAY_CONNECT_PRIVATE_KEY_FILE
  • Environment Variable
  • File
  • Default
  • GATEWAY_CONNECT_PROXY_URL
  • Environment variable
  • File
  • Default
  • GATEWAY_CONNECT_PROXY_USERNAME
  • Environment variable
  • File
  • Default
  • GATEWAY_CONNECT_PROXY_PASSWORD
  • Environment variable
  • File
  • Default
  • GATEWAY_CONNECT_SERVER_HA_ENABLED
  • Environment Variable
  • File
  • Default
  • GATEWAY_CONNECT_SERVER_HA_IS_PRIMARY
  • Environment Variable
  • File
  • Default
Itential Automation GatewayDeploy and manageConfigureConfiguration variables

Connect variables

Was this page helpful?
Previous

Features variables

Next
Built with

GATEWAY_CONNECT_CERTIFICATE_FILE

Specifies the full path to the certificate file used to establish a secure connection to Gateway Manager.

Environment Variable

GATEWAY_CONNECT_CERTIFICATE_FILE

File

Section: connect

Key: certificate_file

Default

/etc/gateway/certificates/gw-manager.pem

GATEWAY_CONNECT_ENABLED

Enables or disables the connection to Gateway Manager.

Environment Variable

GATEWAY_CONNECT_ENABLED

File

Section: connect

Key: enabled

Default

true

GATEWAY_CONNECT_HOSTS

Configures the hostname and port used to connect to Gateway Manager.

Environment Variable

GATEWAY_CONNECT_HOSTS

File

Section: connect

Key: hosts

Default

No default value provided

GATEWAY_CONNECT_INSECURE_TLS

Determines whether the gateway verifies TLS certificates when it connects to Itential Platform. When set to true, the gateway skips TLS certificate verification. We strongly recommend enabling TLS certificate verification in production environments.

Environment Variable

GATEWAY_CONNECT_INSECURE_TLS

File

Section: connect

Key: insecure_tls

Default

false

GATEWAY_CONNECT_PRIVATE_KEY_FILE

Specifies the full path to the private key file that the gateway uses to connect to Gateway Manager.

Environment Variable

GATEWAY_CONNECT_PRIVATE_KEY_FILE

File

Section: connect

Key: private_key_file

Default

/etc/gateway/certificates/gw-manager-key.pem

GATEWAY_CONNECT_PROXY_URL

The HTTP or HTTPS proxy server URL that IAG uses to connect to Gateway Manager. Use the format http://host:port or https://host:port. When you set this variable, IAG routes all Gateway Manager connections through the proxy using the HTTP CONNECT method for TLS tunneling. If you don’t set this variable, IAG falls back to standard system proxy environment variables (HTTPS_PROXY, https_proxy, HTTP_PROXY, http_proxy).

Environment variable

GATEWAY_CONNECT_PROXY_URL

File

Section: connect

Key: proxy_url

Default

None. IAG falls back to system proxy environment variables if available.

GATEWAY_CONNECT_PROXY_USERNAME

The username for proxy authentication. Use this variable with GATEWAY_CONNECT_PROXY_PASSWORD. If you include credentials in the proxy URL (for example, http://user:pass@proxy:8080), those credentials take precedence over this setting.

Environment variable

GATEWAY_CONNECT_PROXY_USERNAME

File

Section: connect

Key: proxy_username

Default

None

GATEWAY_CONNECT_PROXY_PASSWORD

The password for proxy authentication. Use this variable with GATEWAY_CONNECT_PROXY_USERNAME. For security, store credentials in environment variables rather than configuration files. If you include credentials in the proxy URL, those credentials take precedence over this setting.

Environment variable

GATEWAY_CONNECT_PROXY_PASSWORD

File

Section: connect

Key: proxy_password

Default

None

GATEWAY_CONNECT_SERVER_HA_ENABLED

Enable this configuration variable when you have multiple all in one or core nodes for a particular GATEWAY_APPLICATION_CLUSTER_ID. When you enable High Availability (HA), the system runs in active/standby mode. One server connects to Gateway Manager while the others remain in standby mode. If the active node goes down, a standby node connects to Gateway Manager and begins serving requests.

Environment Variable

GATEWAY_CONNECT_SERVER_HA_ENABLED

File

Section: connect

Key: server_ha_enabled

Default

false

GATEWAY_CONNECT_SERVER_HA_IS_PRIMARY

When you set GATEWAY_CONNECT_SERVER_HA_ENABLED to true, use this configuration variable to designate one node as the primary. When all nodes are online, this node takes the highest precedence and connects to Gateway Manager. Only one core HA node can connect to Gateway Manager at a time. If this node loses connection to Gateway Manager or the database, a standby node takes its place.

Environment Variable

GATEWAY_CONNECT_SERVER_HA_IS_PRIMARY

File

Section: connect

Key: server_ha_is_primary

Default

false