cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP POST as sender adapter in Cloud Integration

06-12-2019 1:09 PM
3645 views 3 comments Go to solution
0 Likes
SAP Managed Tags
Subscribe

I have configured an HTTPS adapter as sender in my integration artifact. However, I can only send HTTP GET message to the configured endpoint. When I try and send an HTTP POST/PUT/PATCH I get a 403 unauthorized error.

Using HTTP GET to create data in a backup system just isn't right. How do I allow HTTP POST/PUT/PATCH operations in the HTTPS sender adapter?

0 Likes

Accepted Solutions (1)

Accepted Solutions (1)

engswee
Active Contributor

Hi Iddo

By default, an HTTPS sender channel has CSRF protection enabled which protects against modifying calls such as POST, PUT, PATCH, DELETE.

You have two options:-

1) If you feel that CSRF protection is not necessary for your endpoint, then you can uncheck it

2) However, if CSRF protection is necessary, then your calling system needs to implement a two step approach - first call to retrieve CSRF token, second call (actual call) to POST/PUT/PATCH the data passing in the token from the first call. A missing token is the cause of your 403 error. Coincidentally, vadim.klimov just wrote an excellent blog post on this CSRF issue.

Regards

Eng Swee

Answers (1)

Answers (1)

Former Member
0 Likes

Thanks, that's the missing piece. I read about the new CSRF functionality, but I think SAP poorly explains this part.

engswee
Active Contributor
0 Likes

Yes, unfortunately the SAP Help Portal documentation around it is a bit on the poor side 😞