Power Platform Community Forum Thread Details

I am trying to authenticate an on-premises gateway using an API key. However, I have selected "No Authentication," and as a result, the connector is not working.

The web application is secured using FortiClient, which might be affecting the setup. How can I properly configure the gateway to use an API key for authentication while working with a connector? Are there additional steps required to make it compatible with FortiClient security?

Any guidance or troubleshooting steps would be greatly appreciated.

Thank you!

Categories:

Connector development

@VK-22011302-0

You're running into a known limitation with Power Platform's on-premises data gateway and custom connectors when trying to use API key authentication—especially in environments secured by tools like FortiClient.

Recommended Workarounds

1. Use a Custom Header Instead of API Key Auth
If you control the API:

Change the connector to use "No Authentication".
Manually add the API key as a custom header in each request (e.g., x-api-key).
This bypasses the unsupported API key auth type.

2. Use Azure Relay or Azure API Management
If FortiClient or network policies block direct access:

Use Azure Relay to securely expose your on-prem API without opening firewall ports.
Or use Azure API Management as a proxy to handle authentication and routing.

3. Test with HTTP + Azure AD Connector
If your API can support OAuth2: