1.1 ISC Architecture Overview
Key Takeaways
For a VA-based source, SailPoint sends target operations to the queue for the source’s assigned virtual appliance cluster.
The virtual appliance initiates outbound connections to SailPoint and separately connects to the target system.
A successful appliance-to-cloud connection establishes only one leg of end-to-end connectivity. The connector still needs a working route and credentials for the target.
A SaaS connector communicates with a supported target without a customer-hosted virtual appliance cluster.
The tenant, the appliance, and the target
In SailPoint Identity Security Cloud (ISC), the tenant holds the governance configuration. A source connects that configuration to a system where identities have accounts or access. A source can use a virtual appliance (VA), which is a virtual machine deployed on customer infrastructure. A supported software as a service (SaaS) connector can integrate without a customer VA cluster. When a case mentions a private directory, start by identifying the connector and the network path it needs. A remotely hosted directory can have a private route and need a VA even though its infrastructure is in a cloud.
Aggregation reads source data into the tenant. Provisioning changes the target, according to connector capabilities and configuration. An account may be visible in the tenant after successful aggregation even when a change later fails because the connector’s service account lacks write permission. The appliance bridges connectivity for both directions of data flow. The origin of the network connection and the direction in which data moves are two different things.
How a VA-based request is handled
- The tenant issues a request for an operation such as an aggregation, provisioning change, or connection test.
- The request enters the queue of the cluster assigned to the source. A running VA polls its own cluster’s queue over an outbound connection to the SailPoint cloud.
- The VA that picks up the work communicates with the target system through the applicable connector and reports the outcome. A separate cluster that can reach the target will not receive the request just because it has a valid network route.
The cloud-facing path uses outbound Hypertext Transfer Protocol Secure (HTTPS) over Transmission Control Protocol (TCP) port 443. The appliance also needs name resolution, time synchronization, and access to the required endpoints for its deployment. The source-facing path uses the protocol and port required by the connector and target. For a source that supports Transport Layer Security (TLS), configure and test that option at the source as appropriate. A TLS-protected cloud connection does not establish that the connector uses TLS for every target. Check those settings independently.
| Evidence | What it helps establish | What to check next |
|---|---|---|
| All VAs in the assigned cluster show a connection error | Cloud-facing connectivity may be broken across the cluster | Test shared egress dependencies, including name resolution and required cloud endpoints |
| The VA is connected but only one target fails a connection test | The VA is reporting a connected status | Check target host, connector port, certificate configuration where applicable, and credentials |
| The connector reads accounts, but a group change fails | Read access worked for the aggregation being examined | Check whether the connector supports the write and whether its credential has the required target permission |
| An alternate cluster can reach the target from its network | There is a potential recovery route | Inspect the source’s assigned cluster before assuming the alternate can take the work |
Worked scenario
A company uses a pair of VAs to manage a private directory and a SaaS connector for its ticketing service. After an internal routing change, the directory connection test fails. Both VAs still appear connected and the ticketing integration still works. The engineer should check the route and target port from the assigned VAs first. The ticketing connector exercises a separate path and does not prove that the directory port is reachable. Likewise, opening inbound SSH from SailPoint would leave the affected target path unchanged.
Now suppose the directory connection test recovers and account reads work, but adding a group membership fails with an authorization error from the target. The engineer can use the successful read as evidence that basic connectivity is working. Check write permissions and the exact target operation before changing the network again. A test suite that covers only aggregation would miss this class of failure.
An exercise may specify that an administrator uses Secure Shell (SSH) from an internal management network. That is compatible with an outbound-only cloud connection. The statement concerns who starts the connection between SailPoint and the appliance. It neither describes every port the network team might allow internally nor tells you which target service ports the connector needs.
SailPoint describes the appliance connection model, cluster request handling, and port and endpoint requirements.
A VA is connected to SailPoint. A private directory connection test started failing after a firewall change. Which path should the engineer test first?
The VA-to-directory path on the ports required by the directory connector
Inbound SSH from the SailPoint tenant to the appliance
The browser sign-in route to the ISC tenant
The connection between an unrelated SaaS connector and its target
Two VA clusters can reach the same database. The database source is assigned to Cluster East. Which VAs poll the queue that receives its test-connection work?
Only the two VAs that were most recently added to the tenant
All VAs on the database subnet regardless of cluster
The running VAs in Cluster East
Every VA with the same egress proxy
Sections you finish are checked off in the contents.