Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Saviynt's Integration Paterns

New Contributor III
New Contributor III

Hello All,


I am working on a HLD for a customer and one of the sections I need to fill in is the "Integration Patterns" and "API Security Protocols" Saviynt supports.

Is there a doc or reference guide which gives me this information?





Hi @Mukul  see if the below doc is of any help to you


Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.


For integration methods : Saviynt Enterprise Identity Cloud Connectors (

API  : Generating OAuth Token Using the User Interface (

Manish Kumar
If the response answered your query, please Accept As Solution and Kudos


Here are some common integration patterns supported by Saviynt:

  1. Identity and Access Management (IAM) Integration: Saviynt integrates with IAM systems such as Microsoft Active Directory, Azure Active Directory, Okta, Ping Identity, and others. This integration allows organizations to synchronize user identities, access policies, entitlements, and group memberships between Saviynt and IAM systems.

  2. Human Resources (HR) System Integration: Integration with HR systems like Workday, SAP SuccessFactors, Oracle HCM Cloud, and others enables Saviynt to automate user provisioning and deprovisioning based on HR events such as employee onboarding, role changes, and terminations.

  3. Cloud Application Integration: Saviynt integrates with various cloud applications and platforms, including Microsoft 365, Google Workspace, Salesforce, ServiceNow, AWS, and Azure. This integration allows organizations to extend governance, compliance, and access control policies to cloud-based resources.

  4. Privileged Access Management (PAM) Integration: Saviynt integrates with PAM solutions like CyberArk, BeyondTrust, Thycotic, and others to manage privileged access and enforce least privilege principles across the organization's IT infrastructure.

  5. SIEM and Log Management Integration: Integration with Security Information and Event Management (SIEM) solutions such as Splunk, IBM QRadar, ArcSight, and LogRhythm enables organizations to correlate identity-related events, access activities, and security incidents for threat detection and response.

  6. API and Custom Integration: Saviynt provides APIs and SDKs that allow organizations to develop custom integrations with proprietary or custom-built systems. This enables organizations to extend Saviynt's functionality and integrate it with specific business processes or applications.


API security protocols supported by Saviynt:

  1. OAuth 2.0: OAuth 2.0 is an industry-standard protocol for authorization, commonly used to secure API access. Saviynt may support OAuth 2.0 for authentication and authorization, allowing clients to obtain access tokens for accessing protected resources.

  2. OpenID Connect: OpenID Connect (OIDC) is an identity layer built on top of OAuth 2.0, providing authentication and single sign-on (SSO) capabilities. Saviynt may support OIDC as an authentication protocol, allowing users to authenticate to Saviynt's APIs using their identity provider credentials.

  3. SAML (Security Assertion Markup Language): SAML is an XML-based standard for exchanging authentication and authorization data between identity providers and service providers. Saviynt may support SAML for federated authentication, allowing users to authenticate to Saviynt's APIs via SAML assertions.

  4. JWT (JSON Web Tokens): JWT is a compact, URL-safe token format commonly used for authentication and authorization in web applications and APIs. Saviynt may use JWTs for securing API endpoints, issuing and validating access tokens, and transmitting claims between parties.

  5. TLS (Transport Layer Security): TLS is a cryptographic protocol that ensures secure communication over a network by encrypting data in transit. Saviynt may enforce TLS to secure API endpoints, encrypting HTTP requests and responses to prevent eavesdropping and tampering.

  6. API Keys: API keys are unique identifiers that clients use to authenticate to APIs. Saviynt may support API keys for authentication and access control, allowing clients to include API keys in their requests to authenticate and authorize access to Saviynt's APIs.

  7. Role-Based Access Control (RBAC): RBAC is a method of access control that restricts access to resources based on the roles assigned to users. Saviynt may implement RBAC to control access to its APIs, ensuring that only authorized users with the necessary roles can perform specific actions.

Rushikesh Vartak
If you find this response useful, kindly consider selecting 'Accept As Solution' and clicking on the 'Kudos' button.

Thanks Mate,

Is there a doc link for the information above?