Name: Signing API Request using Bearer Token - SAP Customer Data Cloud
Uploaded: 2020-5-12
Duration: 309 s
Description: In this video you will see how to sign an API request to SAP Customer Data Cloud using a bearer token.

Share feedback

<p>We are aware of intermittent issues in accessing the learning content</p>

We are aware of intermittent issues in accessing the learning content

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?

Please try again later

Sorry, we encountered an error

Try again or reset results to continue browsing

We didn’t find what you’re looking for

To continue, please log in

Your session has timed out

Explore {title} at SAP Learning. Find out more!

Assessment

Course Completion

Knowledge Badge

Certification Exam

Theoretical Exam

External Course

Practical Exercise

Practical Test

External Hands-On

External Resource

Learning Journey

Learning Journey Assessment

Lesson

Live Session

Practice System

Quiz

Course

Stay Certified

Subscription

System Based Assessment

Test Out

Unit

Video

Video Playlist

Week

Enhance your learning experience for free

<div><div>In this video you will see how to sign an API request to SAP Customer Data Cloud using a bearer token.<br><br><br></div></div>

Signing API Request using Bearer Token - SAP Customer Data Cloud

Hello and welcome! In this video, we will talk about signing an API request to SAP Customer Data Cloud using a Bearer Token. The SAP Customer Data Cloud server-to-server API uses a REST-like interface.  This means that the API method calls are made over the Internet by sending HTTP GET or POST requests to the SAP Customer Data Cloud REST API server and the response is returned as JSON. For security reasons, requests to our REST API should always be signed. The recommended best practice is to generate a Bearer Token for the signature,  constructed using a unique RSA key provided on the SAP Customer Data Cloud Console.   An alternative solution is to use Application or User Keys and a Secret. Both methods require creating an Application on the Console, that is associated with a permission group. To get more information about creating and managing CDC Applications, go to enable.cx and search for Creating and Managing Applications.  Note that the RSA Private Key is only available inside the pop-up window when the Application is created.  CDC does not store the RSA secret, if you do not copy it prior to closing the window,  it will be necessary to generate a new key.  Once the App is created you can view the Apps userKey and secret by clicking the edit icon,  which will take you to the app’s Edit Application page. You can sign an API request to SAP Customer Data Cloud using an HTTP Bearer Token.  This replaces the Application or User Key and Secret signature method.  To do so, you should create a JWT, then hash the JWT using the RSA key to create a Bearer Token and sign the API request using that token. Let us show you a quick demo on how to create a Bearer Token and sign an API request using that token. To demonstrate sending an API request, using a Bearer Token for the authentication,  we will use a CDC method for requesting user information accounts.getAccountInfo.  This method retrieves account data for the specified user. We will use Postman to send the request.  To build the request, first, enter the right data center in the request URL.  It is eu1 for this demo. Next, pass the API key of the CDC site, to which we make the request.  Copy the API key from the CDC Console. Then we add the UID parameter to the request.  UID is the unique ID of the user of which we want to retrieve the data.  You can get UID of the user from Identity Access.  Go to Identity Access and open the profile of the user to get the UID.  In our case, it is user Jane Smith. Next, we need to add the Bearer Token to the request. So, let’s create the Bearer Token next.  To do so, create a JWT based on the structure described in the slide.  Go to the jwt.io site and enter the header and body of JWT like stated on the slide.  For detailed explanation about these parameters, go to developers.gigya.com  and search for Signing Requests to SAP Customer Data Cloud. Let’s enter the right values to these JWT parameters.  In the ‘kid’ field of JWT header, copy the User Key from the Application.  “iat” is a timestamp that identifies when the JWT was issued. You can use any timestamp generator to generate the value.  We used epochconverter.com.  Copy the current Unix epoch time to the ‘iat’ field of JWT body. ‘jti’ is a nonce ensuring that this JWT may be used only once.  Since the same ‘jti’ may be used only once, change one figure of its value. To hash the JWT use your private key together with an RS256 hashing algorithm,  along with the header and the body strings, to create the signature You can get the Private Key from the Application.  Copy the private key and paste it into the signature part of the JWT. Now we have the Bearer Token ready.  To pass the Bearer Token in the request, open the Authorization tab in Postman.  Select the type as Bearer Token, and paste the token in the text area next to it.  The getAccountInfo API request is ready. Send the request and check the response.  We received the response with the status code of 200.  This means the call was successful.  We also received the details of the user in the same response. This is how we sign API requests to SAP Customer Data Cloud using Bearer Token. This concludes the demo.  Thank you for watching!