Ask Your Question
0

HTTP client processor failing Oauth 2.0 validation [closed]

asked 2018-03-22 05:28:25 -0500

Fayan gravatar image

Hi team!

I have a workflow which use the HTTP Client as origin and the HTTP Client as processor later on. Both of them connect to the same API to make different calls, both of them have Oauth 2.0 as authentication.

The first one calls the API and receives the answer without issues, the second one is giving me the following error when validating: "HTTP_21 - OAuth2 authentication failed. Please make sure the credentials are valid."

I have created a new pipeline to test the second call with a HTTP Client as origin and it works as expected. I have also tested the call in Postman to make sure the API is not giving me problems.

Am i missing something i should take care of or know when ussing HTTP client processor? Thanks in advance for your help! Regards.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Fayan
close date 2018-04-03 09:37:42.656790

1 Answer

Sort by ยป oldest newest most voted
0

answered 2018-04-03 09:37:31 -0500

Fayan gravatar image

The origin of the problem was that i configured the HTTP Compression to GZip in the second call while the expected is none.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2018-03-22 05:28:25 -0500

Seen: 17 times

Last updated: Apr 03