SCP Workflow Service Task - Headers

[#1]

Hi,

I would like to consume an oData service from within my SCP Workflow. For this purpose, I have made the necessary destination configurations and added the associated values in the workflow's "Service Task properties".

I don't see any placeholders for the oData service request headers such as "X-Requested-With","Content-Type", "Accept" etc. Where should these be configured?

[kavyac]

Hi Tobias, DJ Adams,

Thanks for the information. I can certainly do away with the Content-Type and Accept headers.

The service that I am trying to consume is pretty old and I honestly have no idea as to why it expects the X-Requested-With header as a mandatory field. I have checked around to see if there is any CSRF token generation for these entity sets in place, but there is no such configuration either.

I could see in the link shared by you that the CSRF token check can be switched to use Compatibility Mode for SP02 protection mechanism at SAP CRM level, but this is something that'll have to be done at the sub-node level such as "/sap/opu/sdata/sap" thereby affecting every service within it. I am not well-versed with SAP CRM (the system I am trying to connect to via oData services) to be able to call the shots on it.

So currently the X-Requested-With header is what I will have to work with. Is there any ideal way to proceed with this, or do you have any recommendations w.r.t configurations that can be made at CRM end?

Regards,

Kavya