cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
iso
Advocate III
Advocate III

HTTP connector with Basic authentication bug

Here is the screenshot before running the flow showing the full config of the built-in HTTP connector (no swagger):

HTTP_b4_run.JPG

 

and here is the screenshot of the result of the flow run:

HTTP_after_run.JPG

 

As you can see:  the HTTP connector is set up to send a POST to an API using Basic authentication.  However, it fails in Power Automate but not in Postman, and the error message explicitly refers to oauth.v2 EVEN THOUGH I specified Basic auth! 

Of course it is going to fail if it tries to authenticate against oauth.v2 when the server does not speak oauth.v2!

 

Q1:  Why does this happen? Is it a connector bug when using Basic auth, ie it always defaults to oauth.v2 no matter what?

 

Q2:  Or am I missing something?  I did test the same connector but with a GET request against the data endpoint, plugging in the token and auth cookie from Postman, and that worked, returning exactly the same result I got in Postman.  So why am I unable to get an access-token with Basic auth???  😠😠😠 getting seriously aggravated on this

1 REPLY 1
iso
Advocate III
Advocate III

FYI this curl works as intended. So what is the HTTP connector doing under the covers???
curl_working.JPG

Helpful resources

Announcements
Microsoft 365 Conference – December 6-8, 2022

Microsoft 365 Conference – December 6-8, 2022

Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.

Users online (1,545)