In Cloud Integration iflow , there is a request-reply call to bearer access token provider, then the received token should be used to call and authenticate to another endpoint. This second call fails with 403 HTTP response code.
Similar approach was followed as below for example with using OAuth JWT Bearer:
SAP Cloud Integration
Cloud Integration flow, outbound call, Bearer Authentication, HTTP response code 403 - Forbidden, HTTP 403, Forbidden, Bearer Token, access_token, Authorization Header, bearer prefix, , KBA , LOD-HCI-PI-CON-HTP , HTTP Adapter , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.