Skip to main content

Saviynt

Connector maturity: Beta. See Connector maturity.

Description​

The Saviynt connector uses the Saviynt ECM REST API to bring in Saviynt Enterprise Identity Cloud (EIC) itself - its users, SAV roles and enterprise roles - and, optionally, every endpoint Saviynt governs with its entitlements and the accounts that hold them. OrbisID can also write its privilege and risk classification back to Saviynt entitlements and roles.

System Type Classification​

FieldValue
System TypeIGA Tool
Default Scan Priority500

Version Support​

OrbisID EditionSupported
CommunityNo
ProYes
EnterpriseYes

Supported Protocol​

ProtocolPortNotes
REST API (HTTPS)443 TCPBearer token via OAuth 2.0 password grant

What OrbisID Discovers​

Two independent sides, each with its own tick box under What to bring in:

DataSourceShown in OrbisID as
Saviynt usersPOST /ECM/api/v5/getAllUserDetailsAccounts on the Saviynt system (The IGA tool itself)
SAV roles (Saviynt administrative roles)GET /ECMv6/api/userms/savroles, .../savroles/{name}/usersEntitlements such as SAV ROLE_ADMIN; admin roles are privileged
Enterprise rolesPOST /ECM/api/v5/getRolesEntitlements on the Saviynt system, with the entitlements each role contains as parent/child relationships, and the users assigned to them
EndpointsPOST /ECM/api/v5/getEndpointsChild systems named <this system> - <endpoint> (Systems it governs)
Entitlements and who holds themPOST /ECM/api/v5/getEntitlements (with requestedObject = users)Entitlements and accounts on each endpoint's child system; Saviynt's own privileged flag and risk are kept

With Systems it governs off, entitlements are listed on the Saviynt system itself, as in earlier versions. Accounts on an endpoint are those that hold at least one entitlement there.

Write-back​

OrbisID can write its classification back to Saviynt using Saviynt's own fields:

ObjectPrivilegedRisk levelAPI
Entitlementspriviliged (1/0)risk (number)POST /ECM/api/v5/createUpdateEntitlement
Enterprise rolespriviligedriskPOST /ECM/api/v5/updateEnterpriseRoleRequest
Accounts, usersNot stored by SaviyntNot stored by Saviynt-

The default risk mapping is Low = 1, Medium = 2, High = 3, Critical = 4. Change it in the write-back settings to match your Saviynt risk scale. A risk of 0 means "not set".

NHI Subtype Classification​

This connector does not assert an NHI (Non-Human Identity) subtype directly — accounts are classified via the naming-pattern catalogue rules and AI classifier (Tier B) only. This connector queries global Identities rather than per-target Accounts, and Saviynt's own Account-Type concept lives on a different object entirely, a structural gap outside the scope of connector-level NHI classification.

Connection Requirements​

Required Permissions​

Create a dedicated Saviynt service account with access to the API endpoints.

Minimum permissions:

  • SAV Role with View User and View Entitlement permissions
  • API access enabled for the service account

Credential Mapping​

OrbisID FieldValue
credential.usernameSaviynt service account username
credential.passwordSaviynt service account password
system.ipAddress (the IP Address / Hostname field)Saviynt tenant hostname (e.g., myorg.saviyntcloud.com)

Network Requirements​

The OrbisID server must have HTTPS access to the Saviynt tenant on port 443.

Configuration Steps​

  1. In the Saviynt EIC console, create a service account with read-only SAV Role
  2. Create a Credential in OrbisID:
    • Username: Saviynt service account username
    • Password: Saviynt service account password
  3. Navigate to Systems → Add System
  4. Fill in the fields:
FieldValue
NameDescriptive name (e.g., Saviynt EIC – Production)
OS TypeSaviynt
System TypeIGA Tool
IP Address / HostnameSaviynt tenant hostname
CredentialThe scanning credential
  1. Click Test Connection
  2. Click Save

Troubleshooting​

SymptomLikely CauseResolution
Authentication failedInvalid credentialsVerify service account credentials in the Saviynt console
No users returnedAPI access not enabledEnable API access for the service account in Saviynt
403 ForbiddenMissing SAV Role permissionsGrant View User and View Entitlement permissions
Rate limit errorsToo many API requestsReduce scan frequency or increase the scan interval