Symptom
- Triggering a Cloud Integration flow endpoint happens with Bearer access token as authorization option. With any HTTP clients like Postman, do a call to fetch the bearer access token from SAP BTP Oauth service by performing a POST HTTPS call to https://oauthasservices-<consumer-account>.<landscape host name>/oauth2/api/v1/token?grant_type=client_credentials as steps described in official SAP Help documentation.
- In the next call triggering the integration flow's http endpoint, bearer access token is placed as Authorization Header in Postman, type 'Bearer' and token field contains the access token value.
- All the configuration is correct, but still 403 Forbidden is received as response.
Read more...
Environment
- SAP Cloud Integration
- Neo environment
Product
Cloud Integration all versions
Keywords
Bearer access, access token, access_token, bearer, bearer authorization, oauth authorization, bearer token, oauthasservices, User Role, oauth_client_ , BTP Oauth service, 403, forbidden, 403 Forbidden, oauth_client_, oauth_client_<client ID>, ESBMessaging.send, subscription, iflmap, hcioem , KBA , LOD-HCI-PI-CON-HTP , HTTP Adapter , Problem
About this page
This 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.