User Case :
There are some API's which need OAuth 2.0 policy which is sometimes a custom created API or where we cannot use the direct OAuth 2.0 option in the OIC/ICS Rest Connection.
**Please note SOAP Connection dosent have this . You have to invoke the token API first and pass the access token as header in SOAP Header : Authorization
We have to use the Custom Token Request string here .
This is nothing but a curl statement that you would have executed in Bash to get a response .
-X POST -H "Content-Type: application/x-www-form-urlencoded" -H "Authorization: Bearer YOUR_BEARER_TOKEN_GOES_HERE" -d 'grant_type=client_credentials' https://xxxxxx-dev-zeka.oracleoutsourcing.com/ccadmin/v1/mfalogin
You can compare this to your postman request
This is the curl request which Postman sends.
$access_token automatically extracts the access token from the json response payload.
access_token_usage will be the actual header that will be passed which calling the endpoint defined in the connection, this automatically goes as part of the curl command in backend.
Pls ref https://blogs.oracle.com/adapters/integrate-ics-with-a-third-party-oauth-protected-rest-service-using-the-generic-rest-adapter-part-1
This explains the steps very clear and elaborately .
Feel free to ask any question !
Happy Coding !
There are some API's which need OAuth 2.0 policy which is sometimes a custom created API or where we cannot use the direct OAuth 2.0 option in the OIC/ICS Rest Connection.
**Please note SOAP Connection dosent have this . You have to invoke the token API first and pass the access token as header in SOAP Header : Authorization
We have to use the Custom Token Request string here .
This is nothing but a curl statement that you would have executed in Bash to get a response .
-X POST -H "Content-Type: application/x-www-form-urlencoded" -H "Authorization: Bearer YOUR_BEARER_TOKEN_GOES_HERE" -d 'grant_type=client_credentials' https://xxxxxx-dev-zeka.oracleoutsourcing.com/ccadmin/v1/mfalogin
You can compare this to your postman request
This is the curl request which Postman sends.
$access_token automatically extracts the access token from the json response payload.
access_token_usage will be the actual header that will be passed which calling the endpoint defined in the connection, this automatically goes as part of the curl command in backend.
Pls ref https://blogs.oracle.com/adapters/integrate-ics-with-a-third-party-oauth-protected-rest-service-using-the-generic-rest-adapter-part-1
This explains the steps very clear and elaborately .
Feel free to ask any question !
Happy Coding !