Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Environment Scope: Neo


Technical Requirement – Accessing Cloud Integration (CI) APIs through Client ID and Secret (in Neo). There is slight difference in the way we generate these keys in Cloud Foundry environment.

Following below steps we will see an end-to-end scenario.

  • What will we do here?

    • Adding new Client ID & Secret

    • Adding user

    • Creating dummy HTTPs i-flow in CI

    • Testing HTTPs endpoint through POSTMAN




 

  • Adding new Client ID & Secret


 -> Go to -> Security -> OAuth and register new client



 

-> Give a name, select subscription from the dropdown, authorization grant type, set password and validity of token




  • Adding user


-> Follow the below naming convention to add user (client created in above step) and assign "ESBMessaging" service to send request

Naming convention to follow for user - oauth_client_<client_name>


 

-> Copy the Token Endpoint to fetch token (this will be used in below step while testing through POSTMAN)


 

  • Create dummy HTTP i-flow in CI


-> Design i-flow (sample flow to test the connection)


 

-> Set HTTPs endpoint and Body


 

  • Testing HTTPs endpoint through POSTMAN


-> Fetch token  https://oauthasservices-<Tenant>.hana.ondemand.com/oauth2/api/v1/token?grant_type=client_credentials

-> Select BASIC as Authorization. Pass the secret key generated above.



 

-> Send request to HTTPs endpoint configured above (i-flow).

-> Select Authorization as No Auth

-> Add Header as Authorization (with Value - Bearer <Token generated above>

 


 
We have seen an end-to-end scenario, starting with configuring token (Client ID and Secret) and further, used the same to access CI HTTPs end point.

Any question or feedback will be appreciated!
5 Comments
Labels in this area