Migration Overview​

Migrating to Saviynt from a legacy Identity Governance and Administration (IGA) tool represents a strategic move to enhance identity security, streamline compliance, and improve operational efficiency. This migration is a significant undertaking, requiring meticulous planning, clear objectives, and alignment with both business and technical needs. By adopting Saviynt, organizations gain access to advanced identity and access management features that are scalable, adaptable, and designed to meet the demands of modern regulatory environments and complex organizational structures.

Migration to Saviynt involves transferring identity-related data, roles, access policies, workflows, and governance controls from an outdated system to Saviynt’s modern IGA platform. This process is more than a data transfer; it includes rethinking identity management processes, leveraging Saviynt’s advanced capabilities, and aligning with new security, compliance, and user experience standards. The migration aims to improve security, streamline operations, and enhance user experience.

Introduction​

OAuth 2.0 and OpenID Connect are the most popular and important security protocols for modern API connectivity. While there are many ways to implement OAuth 2.0 and OIDC, a key use case for these protocols is to enable service account authorization for APIs and background tasks integrated with third-party Identity Providers (IdPs) for Single Sign-On (SSO). This allows using an IdP such as Microsoft Entra ID, Okta, or Ping Identity as your IdP for background, service account access to Saviynt Identity Cloud APIs. IdP and SSO support have been a popular request to our product team so we are happy to roll this out.

Specifically, this is implemented using industry standards OAuth 2.0 Token Exchange flow (IETF RFC-8693) and the associated OAuth 2.0 Token Introspection API (IETF RFC-7662). The token exchange can be performed submitting an IdP OAuth 2.0 access token or an IdP OIDC ID token to Saviynt Identity Cloud, which will exchange it for a Saviynt OAuth 2.0 access token. Read more below for an overview and in our documentation for "Configuring OAuth 2.0 Token Exchange Authentication".

Community Connector @ Developer Portal​

In the ever-evolving landscape of software development and integration, the ability to collaborate, innovate, and swiftly adapt to changes is paramount. This is why we have made a significant shift in how we handle our community connectors: moving them from traditional forums and exchange sites to our newly established Developer Portal, which leverages Git as its backend. This transition marks a strategic shift in our approach to managing and disseminating these crucial resources. Here, we’ll explore the motivations behind this move and the benefits it brings to developers and system integrators.