Adding a Connector

Prev Next

The Connector extends connectivity to remote sites and unmanaged resources without requiring a standalone client.

The AppGate ZTNA system supports active-passive high availability (HA) for Connector pairs on traditional networks that support ARP and in AWS.

Connectors also support an internal failover mechanism between multiple Gateways within a Site.

This section describes how to configure Connector appliances.


Before adding a Connector

For details about Connector operation and configuration, see:


Configuring a Connector

To configure a Connector:

  1. In the Add/Edit Appliance page, select the Connector checkbox in the Functions tab.

  2. Complete the following configuration fields:  

Site Settings

  • Appliance Site. Select the Site from the dropdown list.

Resource Group Configuration

A resource group is a collection of local resources that:

  • Share the same access rights, or policy.

  • Have traffic handled by one client instance in a Connector.

Express Connector

An Express Connector is designed for rapid onboarding of new locations, cloud or physical. Express Connectors:

  • Provide immediate access to the location.

  • Are network agnostic.

  • Work across any available ISP, WAN, or SD-Wan connection.

To add an Express Connector, select +Add, then configure the following fields:

  • Get Configuration from Existing Connector Clients. Copies an existing resource group configuration from the other Connector in the HA pair. HA considerations:

    • Using HA has no license implications. Although resource groups appear on both Connectors, licenses are counted only once.

    • Only one set of IP addresses from the IP pool is required. The active appliance hosts the working client, so the same tun IP is used for both Connectors.

  • Name. Enter the group name for the local resources. This value appears as part of the ag.distinguishedName claim that is used in Policy assignment criteria and shown in registered devices.

  • Device ID. Enter the device ID assigned to the client.

  • Local Resources. Enter the IP addresses of the local resources that will be routable through this resource group’s client.

  • Source NAT to local resources. When enabled, traffic uses the Connector’s local IP address instead of the tun IP address. Disabling this causes traffic to appear to be from the user's tun IP address.

  • Destination NAT to a local resource. When enabled, the tun IP address is translated to a local resource IP address, such as the address for a printer. Only one local resource can be specified per resource group.

Advanced Connector

An Advanced Connector is used to protect unmanaged devices that require connectivity to multiple, distributed protected resources.

To add an Advanced Connector, select +Add, then configure the following fields:

  • Get Configuration from Existing Connector Clients. Copies an existing resource group configuration from the other Connector in the HA pair. HA considerations:

    • Using HA has no license implications. Although resource groups appear on both Connectors, licenses are counted only once.

    • Only one set of IP addresses from the IP pool is required. The active appliance hosts the working client, so the same tun IP is used for both Connectors.

  • Name. Enter the group name for the local resources. This value appears as part of the ag.distinguishedName claim that is used in Policy assignment criteria and shown in registered devices.

  • Device ID. Enter the device ID assigned to the client.

  • Local Resources. Enter the IP addresses of the local resources that will be routable through this resource group’s client.

  • Non-DHCP traffic:

    • Source NAT to local resources. When enabled, traffic to local resources uses the Connector’s local IP address. This is enabled by default. Disabling this causes traffic to appear from the user’s tun IP address.

    • Source NAT from local resources. When enabled, traffic from local resources is translated to the client’s tun IP address. This is enabled by default. This must be enabled to use down action rules toward local resources. When disabled, traffic appears to originate from the local resource IP address.

    • Destination NAT to a local resource. Translates the Client’s tun IP address to a single local resource IP address. Only one local resource can be specified per resource group.

    • Default Gateway (forward non-matching traffic). When enabled, non‑routable traffic is forwarded to the Connector’s local default Gateway. Traffic is NATed and appears to originate from the Connector's local IP address.

  • DHCP relay traffic:

    • DHCP Servers. Specify the DHCP servers that provide IP addresses to the local resources defined in this resource group.

High Availability Configuration

Two connectors can operate in an active-passive HA configuration. Select from the following:

  • Assign virtual IP interface for HA Connectors (IPv4)

    • IPv4 Appliance Interface. Select the IPv4 interface for the shared VIP.

    • IPv4 VIP. Enter the virtual IP address shared between the two Connector appliances.

  • Assign virtual IP interface for HA Connectors (IPv6)

    • IPv6 Appliance interface. Select the IPv6 interface for the shared VIP.

    • IPv6 VIP. Enter the virtual IP address shared between the two Connector appliances.

After completing the Connector configuration, continue to the Miscellaneous tab.