Integrations / SailPoint Identity Security Cloud
SailPoint Identity Security Cloud
SailPoint Identity Security Cloud identity governance data for identities, sources, access profiles, roles, entitlements, and account/source mappings.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
SailPoint Identity Security Cloud client-credentials OAuth for a tenant API client. The customer supplies the tenant subdomain, API client ID and secret, and v2024 base URL. Browser authorization-code and refresh-token flows are documented by SailPoint but intentionally not exposed until tenant-aware callback routing is available.
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
- Tenant
- Base Url
SailPoint bearer token. Store base_url as the tenant v2024 API root, for example https://tenant.api.identitynow.com/v2024.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- API token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Identity | Partial — not every record the vendor holds is synced |
| Role | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Identity | Up to 1 day | Removed records disappear on the next full sync |
| Role | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Identity, Role.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty