Name: Introducing OIDC in SAP Customer Data Cloud
Uploaded: 2019-7-2
Duration: 286 s
Description: In this video you will learn the basics of OIDC. The video starts with explaining the key terminologies. Then it explains OIDC in detail and discuss supported and unsupported flows.Visit SAP Customer Data Cloud documentation for more details: https://developers.gigya.com/display/GD/OpenID+ConnectClick here to visit the SAP Customer Data Cloud Community Page.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div>In this video you will learn the basics of OIDC. The video starts with explaining the key terminologies. Then it explains OIDC in detail and discuss supported and unsupported flows.<br><br>Visit SAP Customer Data Cloud documentation for more details: <a href="https://developers.gigya.com/display/GD/OpenID+Connect" rel="nofollow noopener noreferrer" target="_blank">https://developers.gigya.com/display/GD/OpenID+Connect</a><br><br>Click <a href="https://www.sap.com/community/topics/customer-data-cloud.html" rel="nofollow noopener noreferrer" target="_blank">here</a> to visit the SAP Customer Data Cloud Community Page.<br></div></div></div></div></div>

Introducing OIDC in SAP Customer Data Cloud

Welcome to the introduction to the IDC video. During this session, we will introduce the underlying technology and give an overview of the OpenID connect flows, or IDC or OpenID connect. Use as many acronyms and terms, and it is essential to understand what they stand for to understand IDC, ARP stands for Relying Party. This is an application using open ID protocol to authenticate users and request tokens from the OPI. OPI stands for Open ID provider. This is an identity provider providing user authentication to the ARP ID token as a self-contained token representing the outcome of the authentication process. It contains the user identifier as well as user and authentication information. Access token is a token which allows access to resources and can be used to authorize access to user data. Authentication request is the request of an ID token and or an access token from the ARP to the OPI. Scopes and claims are identifiers defining the list of resources and identity attributes, which can be accessed using an access token. Consents are collected within the consent page, which gives the user the option to grant consent to scopes and claims. The token generated will then only have access to these scopes and claims. Oidc functionality can be split into three main pillars. First, the identity layer is the identity management system. Each entity or user can have a different identity depending on the receiving application, and the identity layer is here to share the appropriate level of data to the relying party. For instance, a user could be either a buyer or reseller on an e-commerce website and the list of attributes shared with the website would differ when the user logs on as a buyer or seller. Secondly, the authorization layer. This is basically OAuth 2.0 standard, which comes with a standard list of endpoints used to connect an RBP with an API authorization endpoint is used to authenticate the user and confirm consent. Token endpoint is used in authorization code or hybrid flows in order to generate an access token, an ID token, and or a refresh token. Introspect endpoint is used to have the current status of a token. User info endpoint returns to user identity data from an access token. Finally, ID token is a standard Json web token which can be requested to the authorization endpoint and generated by either the authorization or token endpoints. This is a signed and self-contained token that can contain user profile information. CDC currently supports minimal core functionality. This allows the implementation of the authorization code flow and hybrid flow. The implicit flows do not allow the use of the token endpoint when using response type of ID token. The authorization endpoint generates an ID token only when using response type of ID token. Token. The authorization endpoint generates an ID token and an access token. The access token can be used to retrieve the user details from the user info endpoint. The authorization code flow acquires a minimum of two calls in order to collect the user information. The first call to the authorization endpoint returns an authorization code, and the second call to the token endpoint returns an ID token and an access token that can be used to read the user details from the user info endpoint. The token endpoint requires sign requests with the Ops secret key. Therefore, this flow has the highest level of trust. The hybrid flows are more flexible and allow generating access and ID tokens from the authorization endpoint directly, as well as from the token endpoint. When using response type of code ID token, the authorization endpoint generates an ID token and an authorization code. The authorization code can be used to retrieve an ID token, access token, and a refreshed token from the token endpoint. When using response type of code token, the authorization endpoint generates an access token and an authorization code. The authorization code can be used to retrieve an ID token, access token, and a refreshed token from the token endpoint. When using response type of code ID token token, the authorization endpoint generates an ID token, an access token, and an authorization code. CDC does not support the response type of token, which would return an access token only from the authorization endpoint.