Implementing custom auth for edge functions

Source: supabase/supabase#9642 · opened by @barrelltech

I'm using paddle as a payment provider, and would like to use supabase edge functions to listen to the updates via web hooks. As far as I can tell, this is not currently possible. The three methods for verification I can think of are:

1. Whitelisting the IP addresses paddle uses
2. Decrypting their GPG key they send with every request
3. Adding an authorization header onto the URL

I believe only the last option could work with supabase edge functions, but I can't seem to get the authorization working via a query param. Is there any way to get this working with the current implementation of supabase edge functions? If not, are there any plans to support this sort of use case? I cannot add custom headers via Paddle AFAICT

links to the Paddle docs about their web hooks:

4 years ago