OAuth 2.0 and OpenID Connect

To implement the Digital Identity Management Single Sign-on (SSO) solution, the OAuth 2.0 authorization (authZ) framework and its authentication (authN) extension, OpenID Connect (OIDC) are the most important concepts. OAuth 2.0 was established as a standard way of transferring resources across multiple systems on the internet. However, that standard did not take into account user authentication or user-identifying data. As a result, different organizations would implement their own proprietary means of brokering that information to external systems. To fix this, OIDC was established as an identity-centric extension to the OAuth 2.0 standard. Some of the terms in OAuth 2.0 have slightly different name under OIDC. Moreover, certain types of data that are not standardized under OAuth.2.0 are standardized under OIDC.

Digital Identity Management and OpenID Connect — no relation
Digital Identity Management and OpenID Connect are separate concepts. They are explained as follows: - Digital Identity Management is an identity provider and user lifecycle management service provided by Amdocs. A tenancy under Digital Identity Management includes, among other features, access to a data store in the cloud, and API and Processes that your client(s) uses to perform capabilities (for example, user onboarding, authentication) against that data store. - Open ID Connect (or simply, OIDC) is standardized way of using different APIs to facilitate the transfer of user information and user authentication between two or more clients (for example, a single sign-on portal that then federates user authentication to one or more separate clients). It supplements or extends the OAuth 2.0 framework.
To know more about OAuth and OIDC, refer to the following topics:

Home

Guides

APIs