You’re offline. This is a read only version of the page.
Announcements
4
I've been attempting to create a Custom Connector for Flow to query an internal REST API. I've encountered a couple of issues.
This is the Postman HTTP generated code:
POST /api/v1/blah HTTP/1.1
Host: blah.blah.blah
Authorization: Basic blahblahblahblahblahblah
Content-Type: application/json;charset=UTF-8
Cookie: JSESSIONID=7B43DB0977C71E3447ECC30F3ABC0025
{
"type": "BlahTokenBlah"
}
1. I've found that when you enable the "Connect via on-premises data gateway" option, your security options are limited to "No authentication", "Basic authentication", and "Windows authentication", so the "API Key" option prevents me from entering the "Authorization" in the header. If you try to, you get an error indicating "Authorization" is not permitted in the header and to use the "API Key".
2. No gateways. I have several gateways for SQL, SharePoint, File System and FTP, but when I attempt to create a connection for the Custom Connector, there are no gateways. We have gone over the on premise gateways several times and cannot identify an issue.
Hello,
#1: This is by design as gateway doesn’t support API Key authentication.
#2: The person who installed the gateway at first place should share the gateway with you. This will allow the gateway to be visible and use by other users:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/gateway-management
If its already shared with you, then check with the person who installed the gateway, if he/she can view the gateway when creating custom connector.
Share
Report
All responses (
Answers (
