Its been a long week figuring out how to create a custom connector from PowerApps to a REST endpoint of one of the SaaS apps we use, BUT I'VE DONE IT!
Wahoo! .... theres just one thing...
I'm getting a status code of 200 (which means I made contact with the REST endpoint), but the response shows an error 403, SSL Required.
How do I troubleshoot this?
No clue what your endpoint looks like or what your SaaS app requires, but my initial guess would be that the endpoint requires you to make an HTTPS call? I'd start by checking the endpoint url for https://
Hope this helps,
This is my first (API) rodeo so I'm still on the upside of the learning curve.
The endpoint is https and looks like:
The redirect URL (autogenerated by PowerApps custom connector) looks like:
When I click "Test" in the custom connector, the test URL looks like:
When I first open the app, I have to authenticate to the SaaS using OAUTH2.0 (similar to how you login to Google, etc if you're using their connectors). After that, I test the connection and get the 403 error.
How do I setup SSL between "msmanaged-na.azure-apim.net" (which was auto-generated by PowerApps) and the SaaS endpoint?
Just went back through the "General" tab on the Custom Connector and found I had "HTTP" for the scheme. Updated to "HTTPS", saved connector and tested again, but same results.
I've had some issues in the past where the PA custom connector 'proxy' doesn't match the normal request/response structure defined in the swagger, especially when you're wrapping authentication.
I didn't fix it - but one way to work around it is to set up either a request/response or an HTTPS Flow and test it from there with 'unwrapped' headers.
It's not ideal from a security standpoint, so I wouldn't suggest it as a solution, but it might help to figure out what's working and what isn't.
Like I said though, I didn't manage to get mine working through a native PA custom connector - I eventually had to build an azure function to handle the call which was a bit of a pain. We'll need some of the bigger brains trust from the PA team to step in and advise 🙂
Sorry I couldn't be of more help,
Hm. Yeah, i'm not sure about that. I built this "from scratch" in PowerApps so no Swagger/OpenAPI file.
Here's something interesting:
How do I show the results of an API call in a text box/label/dropdown in the app?
Assuming there is a readable response back to PowerApps, just wrap the call in a Collect() statement - it will still execute the call and anything returned will be placed in the collection which you can view either in the Collections screen, or render on-canvas in a control.
Once you have updated the Schema to HTTPS, please take a try to delete the connection built with the previous custom connector, then create a new one to check.
As the response is a normal 200 OK , there should be no warnings within the PowerApps, Besides, how you defined the Response under the Definition part of the connector?
As @RusselThomas suggested, the result could be saved into a collection.
I did NOT create a response! That was causing some issue for sure. I've since created a default response. Still stuck on the OAUTH2.0 token piece.
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
Check out the winners of the recent 'Can You Solve These?' community challenge!
Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.
Featuring samples like Return to the Workplace and Emergency Response Applications
Features releasing from October 2020 through March 2021