Express Connector

Prev Next

Deploying an Express Connector for access to local resources

The Express Connector provides a simplified way to securely connect users to local resources. It is designed for rapid onboarding of new locations—cloud or physical—using minimal configuration while maintaining fine-grained access control through AppGate ZTNA Gateways.

A Connector is typically deployed as a standalone appliance in a remote location (for example, a cloud environment or branch office). High availability (HA) is supported if required.

Key Characteristics

  • Minimal configuration using Express mode

  • Network agnostic; works across ISP, WAN, or SD-WAN

  • Requires no inbound connections, allowing deployment behind an edge firewall with no infrastructure changes

  • Supports a single Site and connects to all Gateways on that Site

  • Automatically ensures rendezvous between user (up) traffic and Connector (down) traffic

  • Limited to one resource group

  • Automatically assigns a policy and consumes one resource group license

  • Uses the built-in Connector Identity Provider, which requires an IPv4 and/or IPv6 IP pool

  • Automatically creates required down entitlements based on user up rules

  • Requires no manual configuration of policies or entitlements for the Connector client

  • Supports up to 16,000 TCP connections to local resources

NOTE

If local resources must initiate connections (to or through a Gateway), use an Advanced Connector instead.

Basic operation

To configure an Express Connector, see Adding a Connector.

A resource group represents a set of local resources that:

  • Share the same access rights (policy)

  • Have traffic handled by a single Connector client instance

Each resource group configuration includes:

  • Name

  • Local resources

  • Optional Source NAT and Destination NAT settings

  • An automatically created Device ID for the Connector client

Each Connector runs multiple headless Linux client instances. Each client:

  • Is associated with a single resource group

  • Receives a unique policy

  • Connects to all available Gateways on the allowed Sites

  • Runs in an isolated Linux namespace to maintain traffic separation

Each Connector client consumes one IP address from the assigned IP pool (which can be separate from user IP pools). Ensure the pool is large enough to support all configured resource groups.

Connector clients use concealed profiles and credentials and automatically attempt to sign in to the Controller on startup. A valid policy must exist for these clients. Otherwise, repeated sign-in attempts can generate excessive log entries and place unnecessary load on the Controllers.

Primary use case - Down traffic from users to local resources

Diagram illustrating network connections, gateways, and user entitlements for remote access.

Down rule flow

  1. User connects to a Gateway on the Site.  

  2. A VPNd process enforces entitlement actions on the user’s traffic.  

  3. Matching down rules are automatically created for the Connector client based on the user’s entitlements on that Gateway.

  4. Traffic is forwarded tun-to-tun between the user and Connector client.  

  5. A VPNd process on each Gateway handles traffic from Connector clients.

  6. All Connector clients connect to all Gateways on the Site.  

  7. The Connector client receives traffic destined for local resources.  

  8. The resource group defines which local resources are reachable.  

  9. Traffic is forwarded to local resources using Source NAT or Destination NAT, as configured.  

  10. Local resources must be able to route return traffic back to the Connector.

Configuring Down access

Diagram illustrating network connections between local resources, connectors, and gateways with IP addresses.

Connector configuration

  1. Enable the Connector function on the appliance.

  2. Select the Site to associate with the Connector.

  3. Under Resource Group Configuration, add a new resource group:

    1. Specify a name (for example, printerA).

    2. Define the local resource IP address (for example, 192.168.8.10).

    3. Leave Source NAT to Local Resources enabled unless the local resource must see the user’s tun IP.

  4. If deploying an HA configuration, assign a VIP under High Availability Configuration.

Local resource configuration

If Source NAT to Local Resources is disabled, traffic from the Connector appears to originate from the user’s Client tun IP. In this case, ensure return routing is configured:

  • On the device: add a route for user client tun IPs via the Connector

  • On the router: add a route for user client tun IPs via the Connector

  • In cloud environments (AWZ, Azure), additional configuration is typically required:

    • Add a route on the local subnet for source IPs via the Connector

    • Allow the Connector NIC to accept traffic not addressed to itself:

      • In AWS, disable "Source/Destination Check".

      • In Azure, enable "IP forwarding" on the network interface.

Identity provider

Ensure the built-in Connector identity provider has IPv4 and/or IPv6 IP pools assigned for Connector clients (for example, 192.168.100.0/24). Default pools can be expanded if additional tunnel interfaces are required. See IP pools for details.

Entitlements

Create a user entitlement allowing up traffic to the local resource (for example, TCP up to 192.168.8.10].

NOTE

AppGate ZTNA recognizes this IP address as a Connector-protected resource and automatically adds the user's tun IP as a source in the generic down rule from the Gateway to the Connector client. This rule allows all protocols (TCP, UDP, GRE, and others).

Policy

  • Create a user policy that includes the up entitlement.

  • The policy for the Connector client is created automatically.

Dashboard

  • Verify the Connector function is healthy on the appliance status dashboard. This confirms the Connector client is signed in and has entitlements assigned.

  • From Session Details:

    • Locate the Connector client by name.

    • Verify allowed entitlement actions.

    • Check User Claims > ag to confirm the correct connectorSubnets are present.

User

When Destination NAT to Local Resources is enabled:

  • Users send traffic to the Connector client’s tun IP, not the local resource IP

  • Tun IP allocation is stable and typically does not change

  • Each tun IP maps one-to-one with a specific local resource

  • The Connector performs SNAT toward local resources, making traffic appear to originate from the Connector IP

This approach avoids conflicts when multiple Connectors protect overlapping IP ranges by using unique tun IPs.

Diagram illustrating network connections and IP addresses for local resources and gateways.

NOTE

Only one local resource can be specified per resource group (one IPv4 and one IPv6).

Test user access after configuration to confirm connectivity.

SSH access to a Connector

SSH access to a Connector without a fixed or public IP address requires a specific configuration. Refer to SSH command line access for details.