OAuth bearer token issues with HTTP Actions

[David59740]

I am using an API for a website called Beacon: Swagger UI (beaconproplus.com) (API documentation).

My goal of contacting this API is to get the pricing of items on Beacon's site. To do this I first have to login with an HTTP Post Request which works just fine. After that, I am attempting to get the pricing of the items using the /pricing parameter on a second HTTP GET request but I am failing.

The result of my second HTTP is always error code 401: "Unauthorized, the authorization bearer token is invalid." The documentation on the website says that the API uses OAuth authorization and that I need a bearer token to access the service. Is this generated from the first HTTP action login request? Any help would be much appreciated.

Edit: After doing some digging I found that I am returned a JWT from the first HTTP but I'm still having issues passing this token into the second HTTP.

[David59740]

To further explain my issue here are some things I have gathered

1. JSESSIONID (This is dynamic for every new login, this is the unique session of my HTTP calls and I think I need to pass this to my second HTTP)

2. RememberMe output from Set Cookie output of first HTTP (This is the JSON Web Token from my initial login request)

3. When I add the header - Authorization: Bearer 'JWT'  the result from the HTTP says 

                                           "Authorization": "*sanitized*", I don't know what this means

I have tried every combination with this and am not sure this is possible. I have tried putting the JSESSIONID in the Set Cookie of my GET request and my access token in my Authorization Header and it still does not authenticate me. Is maintaining a login using OAuth even possible on Power Automate? I have hit a wall, does anyone know anything about this? 

[mleonardi84]

Hi, 

i have the same problem. Did you resolve this problem?

[David59740]

No, we moved to a Python script instead. From what I can tell this specific case was not possible in Power Automate, but then again, I never received a response so I'm not positive.

[Ajinder31]

Hi @David59740 , Have you tried it with rest clients like Postman etc? If Yes, was it working as expected?  

[David59740]

I did not use Postman but I believe that would work. Power Automate fails because the API authenticates the session but there's no solid way to make additional API calls while referencing the authenticated session.

[Ajinder31]

I am not familiar with the Beaconplus API and its working so can't say much but Power Automate does worked for me with OAuth and token based API endpoints.