You’re offline. This is a read only version of the page.
I've created a new custom connector to link to an instance of Atlassian Confluence Server, however my tests are consistently failing with a 403 error.
The security for the connector is set up as "API Key", with the Parameter Name "Authorization" and the Parameter Location as "Header".
I have managed to successfully call the API via Postman using the request body generated by Power Automate during the test, but I think the Authorization header parameter is wrong.
I am using an API key to authenticate and have used the following header parameter in Postman:
Share
ReportBearer Ho0xvy***************************************However no matter how I set up my connection in Power Automate, the header always contains a much longer different key:
Bearer eyJ0eXAiO**************I can't fathom why Power Automate is not just passing the API Key that I give it and after recreating both the connection and the connector several times I'm stumped.
Has anyone come across this before or does anyone have any advice on how to fix it?
Cheers,
Freddie
I have got the same error, I have tried with differents API (Pass2u/ Passkit) to create a pass from PowerAutomate neither of the two works, and answer me the same error 403 with "error from cloudfront".
Looks like request HTTP from PowerAutomate can't access to the server even if I set authorization header with my API KEY.
While in Postman it worked.
I think there is something missing in the configuration of the custom connector...
All responses (
Answers (
2
