1.5 Virtual Appliance Network Configuration

Key Takeaways

  • SailPoint documents standard direct egress, an HTTP proxy, and a network tunnel for different network requirements.

  • An HTTP proxy routes VA HTTP and HTTPS traffic through the configured proxy. Approved internal HTTP targets can use a documented bypass.

  • Allow the required cloud endpoints for the applicable region as well as the common endpoints. The destination port alone does not establish that egress works.

  • Check Domain Name System resolution, clock synchronization, and certificate trust independently when troubleshooting otherwise reachable endpoints.

Last updated: November 2026

Translate a firewall policy into a deployment choice

A virtual appliance (VA) needs ongoing outbound access to SailPoint and supporting endpoints. It also needs an approved path to the systems connected through its cluster. Begin by asking where the cloud requests will go and how the appliance will reach its sources. Those answers can differ even when both kinds of traffic use Hypertext Transfer Protocol Secure (HTTPS).

Network policyConfiguration to evaluateWhat to prove in testing
Firewall permits direct outbound HTTPS to the required domainsStandardEach VA reaches the endpoint list and the connector reaches the target service
Outbound web traffic must pass through an approved proxyHTTP proxyProxy access and allow-list coverage work for the VA and its HTTP or HTTPS targets
Egress requires an allow list, and the firewall cannot accept domain entriesNetwork tunnelThe region’s documented tunnel destinations are permitted and target connectivity still works

The Hypertext Transfer Protocol (HTTP) proxy configuration and the network tunnel are incompatible on the same VA. For standard and proxy designs, use the requirements page’s domain list and account for region-specific endpoints. SailPoint does not support IP allow-listing for connected service endpoints. The documented tunnel configuration has its own regional HTTPS destination requirements. A policy that permits a public service’s current DNS result can break if that result changes. A tunnel uses its prescribed endpoint design, so follow that procedure instead of building an IP inventory of cloud dependencies. Check that any selected appliance components support the egress choice.

Get beyond a single port test

The network requirements list outbound Transmission Control Protocol (TCP) port 443 for HTTPS and access to name resolution and time synchronization. Domain Name System (DNS) resolves the cloud and target names for the paths that use it. A Network Time Protocol (NTP) source keeps each appliance’s clock synchronized. If policy prohibits external NTP, configure each appliance to use an approved internal NTP server before closing the external path. Check the settings and actual clock status on each affected appliance.

Endpoint lists can include common hosts, required US East endpoints, and endpoints for the tenant’s own region. For example, a non-US-East tenant needs the Amazon Simple Queue Service (SQS) endpoint identified in SailPoint’s requirements for its region as well as the documented US East endpoint. A test to a generic HTTPS site may pass while the VA still cannot poll its queue. Check the actual destinations from the same path the VA uses. If a proxy performs Transport Layer Security (TLS) inspection, confirm the appliance trusts the applicable root certification authority using the supported configuration. Basic TCP connectivity does not prove that the TLS peer will validate.

For example, a certificate error starts after an egress proxy is updated, but the VA can still resolve and reach the intended endpoint. Collect the certificate chain seen on that path and compare it to the approved authority configured for the appliance. A different diagnosis applies when the clock is out of sync. Verify the clock and certificate validity dates before changing the trust configuration.

Worked proxy example

A company chooses an HTTP proxy because direct cloud egress is prohibited. The appliance can reach SailPoint through the proxy, but a connector must call the private application at hr-api.example.org. The company’s proxy cannot resolve or route to that private destination. The network team permits the appliance to reach it directly. In this case, the documented no_proxy entry in proxy.yaml can exempt that host, preserving proxy egress for cloud traffic.

Confirm the hostname matches what the connector uses. Check name resolution for that hostname on the VA and verify the direct route, target port, and certificate chain. Repeat the connection test for the target. A successful test demonstrates that this target works with the intended route. It gives no evidence about other URLs or about how a different member was configured, so test each path needed by the deployment.

If a test question changes that premise so direct access to the local application is forbidden, the bypass no longer fits the use case. Work with the network team to establish an approved path through the proxy or use a supported connector and network arrangement that meets both requirements. Adding a bypass entry cannot grant a route through a denying firewall.

For current allowed destinations and supported settings, use SailPoint’s system and network requirements and proxy and tunnel configuration.

Test Your Knowledge

The firewall must use an outbound allow list and accepts only IPs. Which SailPoint VA configuration should the engineer evaluate for cloud traffic?

A

A public inbound port to the VA for every cloud endpoint

B

A static list of DNS results from SaaS endpoints in the standard configuration

C

The documented network tunnel configuration for the tenant region

D

An HTTP proxy and network tunnel both enabled on the same VA

Test Your Knowledge

A VA’s HTTP proxy can reach SailPoint but cannot route to a private source’s HTTPS API. Direct VA access to that private hostname is authorized. Which adjustment preserves the proxy for cloud traffic?

A

Add a documented no_proxy entry for that hostname and verify the direct route

B

Replace the VA’s cloud endpoint with the private API hostname

C

Open inbound TCP port 443 from SailPoint to the VA

D

Disable source-side TLS so the proxy can resolve the private name

Sections you finish are checked off in the contents.