2.1 Source Configuration
Key Takeaways
Source configuration determines how SailPoint reaches the system and what operations its connector supports.
An identity profile makes a source authoritative for identity creation. Connectivity and provisioning capability are separate choices.
A direct connection can use a VA-based connector or a SaaS connector. A flat file source instead imports data provided in a file.
Quick Compliance provides read-only account and entitlement aggregation. Verify a Deep Governance connector’s write capabilities and test the configured actions in a controlled setting.
Identify the decisions behind each source
A source is SailPoint’s representation of an application, directory or other system that maintains its own accounts or personnel records. Start by asking whether the source will provide records used to create identities, how the connection will reach the system, and whether the integration needs to change access. Each answer concerns a different setting. A human resources (HR) source can provide authoritative personnel data over a read-only connection. A non-authoritative directory can be write-enabled to manage employee accounts.
When a source has an identity profile, it is authoritative. Its accounts provide input for creating identities. Other sources can still supply accounts, access data and mapped values for those identities. Changes to access and lifecycle treatment follow the profile’s mappings and configured access behavior. Choosing a connector type alone does not define who joins, whose account matches, or what happens when someone leaves.
Compare the supported connections
| Requirement | Source option to evaluate | Verify before choosing |
|---|---|---|
| Govern a private system reachable from customer infrastructure | A VA-based connector for that source type | Which supported connector, assigned cluster, protocol, route and target permissions are required |
| Connect to a supported service through SailPoint-hosted connectivity | A SaaS connector | Supported endpoints and authentication, product features and specific operations |
| Load account information from an export when there is no direct integration | A flat file connection | Required columns, import ownership, refresh frequency and handling of manual changes |
| Collect accounts and entitlements for visibility with a read-only integration | A Quick Compliance connector | Supported objects, data quality and schedule |
| Write changes using a supported connector | A Deep Governance connector, VA-based or SaaS | The exact write operations, their prerequisites and the configured provisioning setting |
SailPoint’s virtual appliance (VA) documentation describes an appliance for systems that require customer-managed connectivity. The SaaS connector model does not use a customer VA cluster. A SaaS application may have more than one SailPoint connector offering. Verify the selected connector variant and its documentation before assuming it can perform an operation. The source being hosted in a cloud is insufficient to select that connector.
SailPoint’s standard source setup documentation describes new sources as read-only by default. On applicable sources, Enable Provisioning in Base Configuration allows configuration of supported provisioning operations. The current standard setup instructions say deselecting the toggle returns that source to read-only. That setting controls future write capability. Previously applied target changes need separate reconciliation if they should be reversed. A source with the Quick Compliance badge cannot be used for direct provisioning.
Work through an onboarding decision
Operations wants to inventory accounts and groups in a hosted application this quarter. It plans to automate granting and revoking group memberships later. A supported Quick Compliance integration can meet the initial visibility requirement, assuming it provides the required records. The later phase needs a connector variant that explicitly supports those writes. Before relying on the same integration for both phases, confirm that the source can support the intended configuration. A successful read-only connection test is useful evidence about authentication and reachability. It cannot show that the integration is authorized to modify group membership.
A second application provides only a weekly comma-separated values (CSV) export. Use the supported flat file connection and check its account schema against the export. Source owners can receive manual provisioning tasks for flat file sources. Completing the target change through an operator and then importing a current export are different actions. The file is an input to SailPoint. It does not issue a command to the external application.
Validate the new source
Select a source owner, inspect the connector’s supported capabilities, and enter authorized connection data. Test connectivity as applicable and verify a small set of representative accounts and entitlements after loading them. Compare attributes and memberships to the target. For a planned write-enabled integration, test the specific create, grant or revoke action in an appropriate controlled setting and inspect the outcome on the target. Check the account and entitlement aggregation processes separately as applicable. Connector-specific requirements determine which objects and operations the source can support.
See SailPoint’s connection and connector definitions, source configuration, and authoritative source and identity profile setup.
A read-only pilot uses a Quick Compliance connector. The next phase requires automatic group revocation on the target. Which design change addresses the new requirement?
Choose a connector variant with Deep Governance support for that revocation and test its write configuration
Increase Quick Compliance account aggregation frequency
Designate the Quick Compliance source as authoritative for identity creation
Enable provisioning on the existing Quick Compliance connector
A team used Enable Provisioning on a supported source configured with Standard Setup. It now needs to return that source to read-only. What does SailPoint’s documented setting allow?
Deleting the authoritative identity profile is the required control
Reading the account schema automatically restores read-only access
Deselecting Enable Provisioning returns the source to read-only
Choosing Quick Compliance is the only way to end writes because the toggle is irreversible
Sections you finish are checked off in the contents.