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
| Field | Value |
|---|---|
| System Type | IGA Tool |
| Default Scan Priority | 500 |
Version Support
| OrbisID Edition | Supported |
|---|---|
| Community | No |
| Pro | Yes |
| Enterprise | Yes |
Supported Protocol
| Protocol | Port | Notes |
|---|---|---|
| REST API (HTTPS) | 443 TCP | Bearer token via OAuth 2.0 password grant |
What OrbisID Discovers
Two independent sides, each with its own tick box under What to bring in:
| Data | Source | Shown in OrbisID as |
|---|---|---|
| Saviynt users | POST /ECM/api/v5/getAllUserDetails | Accounts on the Saviynt system (The IGA tool itself) |
| SAV roles (Saviynt administrative roles) | GET /ECMv6/api/userms/savroles, .../savroles/{name}/users | Entitlements such as SAV ROLE_ADMIN; admin roles are privileged |
| Enterprise roles | POST /ECM/api/v5/getRoles | Entitlements on the Saviynt system, with the entitlements each role contains as parent/child relationships, and the users assigned to them |
| Endpoints | POST /ECM/api/v5/getEndpoints | Child systems named <this system> - <endpoint> (Systems it governs) |
| Entitlements and who holds them | POST /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:
| Object | Privileged | Risk level | API |
|---|---|---|---|
| Entitlements | priviliged (1/0) | risk (number) | POST /ECM/api/v5/createUpdateEntitlement |
| Enterprise roles | priviliged | risk | POST /ECM/api/v5/updateEnterpriseRoleRequest |
| Accounts, users | Not stored by Saviynt | Not 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 UserandView Entitlementpermissions - API access enabled for the service account
Credential Mapping
| OrbisID Field | Value |
|---|---|
credential.username | Saviynt service account username |
credential.password | Saviynt 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
- In the Saviynt EIC console, create a service account with read-only SAV Role
- Create a Credential in OrbisID:
- Username: Saviynt service account username
- Password: Saviynt service account password
- Navigate to Systems → Add System
- Fill in the fields:
| Field | Value |
|---|---|
| Name | Descriptive name (e.g., Saviynt EIC – Production) |
| OS Type | Saviynt |
| System Type | IGA Tool |
| IP Address / Hostname | Saviynt tenant hostname |
| Credential | The scanning credential |
- Click Test Connection
- Click Save
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|---|---|
Authentication failed | Invalid credentials | Verify service account credentials in the Saviynt console |
| No users returned | API access not enabled | Enable API access for the service account in Saviynt |
403 Forbidden | Missing SAV Role permissions | Grant View User and View Entitlement permissions |
| Rate limit errors | Too many API requests | Reduce scan frequency or increase the scan interval |