Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Apps - Connector Development
Unanswered

How to Authenticate On-Premises Gateway Using API Key?

(1) ShareShare
ReportReport
Posted on by

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:
  • Suggested answer
    Jon Unzueta Profile Picture
    759 on at
    How to Authenticate On-Premises Gateway Using API Key?
     
    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:
    • Use the HTTP with Azure AD connector, which supports the gateway 
    • This requires registering your API in Azure AD and using client credentials flow.

    🧪 Troubleshooting Tips
    • Check FortiClient logs for blocked or redirected traffic.
    • Use Postman from the same machine as the gateway to test API access.
    • Enable gateway logs to trace request failures.
     If the response is helpful to you, a like or mark as the correct solution. thank you so much!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Michael Gernaey – Community Spotlight

We are honored to recognize Michael Gernaey as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard >

Featured topics