We have some webhooks from external entities that we want to react to and log. One would be posting within a teams channel, the other would be sending an http request to a custom end point. Those parts are fine, the issue is really with this connector and the half-assed approach behind it.
Very few companies use oauth for webhooks, it's so few it's practically none. Most force us to use either basic auth and/or hmac, or no security. Now, maybe there is a way to configure this connector to use basic auth or hmac (i.e. secret), but I have not been able to figure out how (not get results searching). Basic auth would mean adding user+pass to the url. It's not the most secure thing in the world, but better than nothing. For hmac, I could parse the ehader to get the key, but I cannot find a way to the calculation without an external component, but maybe I am not being creative enough.
It seems to me like basic auth should always be supported, it's not going away, not any time soon anyway.
Hi,
I found a post on the Power Platform Community forum that discusses how to create a flow with HMAC authentication. The post suggests using an HTTP post trigger and provides an example of how to send a Bearer token in HTTP. You can also check out this post on the same forum that explains how to validate a webhook message using HMAC/Signing Key in Azure Logic App.
If you want to skip the Power Automate part and do the authentication and utilize the external service in Power Apps only, you can create a custom connector for it. You can check out this link for more details on getting started to create a custom connector.
Gill