Defining hosts

Prev Next

Admins define access rules by creating entitlements. Each entitlement includes one or more actions. In each action, a host is defined using an IP address (or subnet), hostname, URL, resource name (cloud resolver), or entitlement script.

Hosts can be a target (up rules: client to Gateway) or a source (down rules: Gateway to client). For details on each host type, see:

  • IP addresses and or ranges. Protected hosts defined by IP.

  • Hostnames. Typically resolved using internal DNS.

  • URLs. Used with URL access (HTTP up action type).

  • Resource names. The Gateway discovers allowed IP addresses from the hosting environment for the entitlement (not for protected URLs).

  • Entitlement scripts. Populate protected hosts based on claims or external attributes. If a script returns a resource name, the Gateway discovers and uses the allowed IP addresses for that entitlement.

The system can handle normal DNS changes (for example, when autoscaling adds an instance). Avoid host definitions that resolve to large numbers of IPs that change frequently. Gateway updates are queued per user, so frequent changes can create large queues (for example, 500 users × 20 changing actions = 10,000 updates). Use host definitions that resolve to stable values for your environment..