You’re offline. This is a read only version of the page.
I have created a custom connector that is connecting to a vendor's API. I have unauthenticated GET methods working, but now am working on some POSTs and am running into an issue with putting "Authorization: Bearer token_value" in the header. Even on the unauthenticated GET calls, I can see in the request header that "Authorization: Bearer some_token_value" is already there. I've tried setting the Header in my POST call, but then I get the error: "Message": "Error from ASE: Bad authorization header scheme".
I can see that the request header has my token_value and so it appears I'm not allowed to set the header that way. What is the right way to send my "Authorization: Bearer token_value" to the API?
Thank you.
Unfortunatly the solution explained by @Yoshi1 and @LaelLeeH doesn't seem to work anymore. (btw thanks for your posts!!)
The policy doesn't get executed, and the "Authorization" value remain unchanged, no matter what value the policie is supposed to give it (wanted to replace Bearer by Basic here -> maybe thoses options doesn't work with a Basic Authorization value.... ?).
However! I'm working with an httpS:// URL so MAYBE the policie doesn't work on them since it's title is "Set HTTP header". Would be logical although quite suprising.
Second option that is to set the security at API Key and give it "Authorization" as a parameter name and
"Bearer YOUR_BEARER_TOKEN_VALUE" as a value when creating the connexion doesn't work either. The connector ignore it and still send the generated Authorization value
Advice to any reader, open Power Automate ^^'
Hi, I tried this approach but it doesn't work for me. I have a local gateway setup for an internal api that needs to authenticate using bearer token.
Everything looks okay but I get a 400 as respose. Any help here would be greatly appreciated.
@Anonymous, I'm getting the same behavior. Did you ever figure it out?
Hello,
I lost two days just to figure it out that in access-token you should not only post the token. The value that goes in access-token is "Bearer access-token" no double quotes.
Thanks for the solution
For some reason both headers are being sent (with different values?!), which causes failures in my call:
Does anyone know what can I be missing? I've selected 'No Authentication' in the Security tab.
Hi @Anonymous ,
I have the same problem like you. I have a an API from a service and I need to call it. In order to do this they have another url with basic auth in order to get a bearer token and then use it as authorization in my call. I am not a developer and doing this for my family business.. Do you mind if you can guide me how you did that step by step?
@Yoshi1 Did you get this to work even on "Get" Requests? Or only on "Post" Method?
#1
lbendlin
7
Super User 2025 Season 1
#2
Michael E. Gernaey
6
Super User 2025 Season 1
#3
KT-07051015-0
4
Share
Report
All responses (
Answers (