Answered

Custom Connector and Auth problems in PowerApps only

(0) Share

Report

Posted on by BrianCCampbell

103

I have powerautomate http request endpoint (Put) (tested with postman successfully) that I created a custom connector for. In the PowerApps Custom Connector web page I can test the connector and it works successfully. I specified default values for almost all parameters and as a result, in the PowerApp I am calling the custom connector and passing in the two expected parameters that powerapps prompts me to. These two parameters are a number (float) and a string. No matter how I specify them in Powerapps I get the following message below. The one thing I noticed after chasing down all the google leads for this is that the string parameter is passed in the body of the request as opposed to the other parameters that are specified in the query. I have exported and created the custom connector as a new one, saved and signed out of powerapps so I get prompted to allow access to the custom connector and I don't know what else to try. Anyone have any insight or encountered this with a custom connector? I should probably add that the custom connector is attached to that http request put endpoint in powerautomate and all it is doing is displaying the input with the trigger compose command (not using any user's shared resources like some others have discussed with this problem). Oh yeah - there is no auth specified for the connector in step 2 - it is set to none.

{
"error": {
 "code":"AuthorizationFailed",
 "message":"The authentication credentials are not valid."
 }
}

Thanks,

Brian

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Sort by

TheRobRush 11,128 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Not sure if you have already, if so ignore me, but you might have more luck if you also post this in the PowerAutomate forum at Microsoft Power Automate Community Forums

Was this reply helpful? Yes No
Verified answer

BrianCCampbell 103 on at

Like
a
(0)

Report
Copy link

Link copied!

I left it alone and came back to it and pretended like it never happened. I got almost to the same point as above and then got past one hurdle. The thing that was throwing the error was a parameter that was being passed in using backslashes "\". I am not sure if it was postman or the connector importing from URL but it changed the backslashes to %2F for each one. Once I changed those ASCII representations back to a regular backslash I got a different error 😀 - but that's the name of the game. If you are curious about the next hurdle you can read about it here on the PowerAutomate side of the house.

Was this reply helpful? Yes No