When a new supabase function is created or edited the default behavior seems to be to enable Verify JWT with legacy secret. Supabase recommends that this be OFF with JWT and additional authorization logic implemented inside your function's code. This old legacy way is deprecated.
This is constantly breaking every edge function that is created that is accessed from outside of Supabase and I am having to manually turn this off on all public facing Supabase edge functions after they are updated.
Can you update the system prompt to keep this disabled please? Thank you.
When a new supabase function is created or edited the default behavior seems to be to enable Verify JWT with legacy secret. Supabase recommends that this be OFF with JWT and additional authorization logic implemented inside your function's code. This old legacy way is deprecated.
This is constantly breaking every edge function that is created that is accessed from outside of Supabase and I am having to manually turn this off on all public facing Supabase edge functions after they are updated.
Can you update the system prompt to keep this disabled please? Thank you.