We are in the process of testing out the SAP CP Workflow Service. We want to consume, via a Service task, an OData service registered via OData Provisioning.
We previously had an issue with this and had to wait for SAP to provide a way to access OData from Workflow via OAuth2. The latest update from SAP provided this ..
However, we are facing an issue when we tried using this. Just a background, we authenticate via our corporate LDAP. So, when we access the OData directly via https://gwaas-<full URL>, we get redirected to the SAP Cloud identity service for authentication.
So, back to the workflow ... we followed the details in the help as above but we are getting an issue with the workflow (see below)
Thanks for the reply ... that is actually part of my main question ... if we have the URL https://gwaas....<service-name>; ... how do we call that via OAuth? When call the URL https://gwaas, we are redirected to the SAP Cloud Platform Identity Authentication service because we configured it that way ... so, what is happening (I believe) is that when the workflow service task calls the OData service, it is actually being presented with the logon screen ... that's just an assumption though ...
What I was after is some sort of guidance how we can call the OData service we have via OAuth ... so that then we can use the OData service in our workflow config.
according to our logs, the service you are calling is still responding with http 403 It is not ideal that you don´t see the actual cause directly yourself. Were you able to call the service using OAuth from the browser?
Would you be able to assist me on this? Somehow, the help documentation on how to use OAuth to access OData services on OData Provisioning via a service task in SCP Workflow is not working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.