Use Gateway Configuration in Admin Essentials to configure how integrations execute through your customer-hosted Itential Automation Gateway 5 (IAG 5) deployment. Outbound API calls originate from your IAG 5 environment rather than from Itential’s cloud, so they pass through your existing network controls.
If your network requires outbound traffic to pass through a proxy server, you can configure it here once and all integrations inherit it by default.
At least one gateway cluster running IAG 5 version 5.4 or later must be registered in Gateway Manager. For information, see Gateway Manager overview and Create a gateway cluster.
Use the Platform Default section to designate the default gateway cluster that all IAG 5-dependent features inherit when no feature-specific cluster is set.
To set the Platform default cluster:
Some considerations:
Feature-Specific Execution Defaults lets you choose a different gateway cluster for a specific feature, such as integrations, and configure additional settings for it. These settings apply to all integrations by default. Individual integrations can override the cluster and proxy settings configured here. For more information, see Manage integrations.
By default, integrations use the Platform default cluster. To route integrations through a different cluster:
The Default Execution Mode setting controls how integration requests are routed. Each integration can override this setting from its own configuration page.
Under Integrations, select one of the following from the Default Execution Mode dropdown:
If you selected Default cluster with proxy, configure the following fields:
Platform supports HTTPS proxies only.
For Proxy authentication type, configure one of the following: