Feature request
Supabase has made clear their intent to migrate customers to the new Publishable and Secret API Keys. To maintain functionality moving forward, the ability for this package to use those keys is important
Describe the solution you'd like
Ability to authenticate Client.Auth, Client.AdminAuth, etc, with the Publishable or Secret keys instead of the anon or service role keys. Currently, if you simply try to pass the API keys in, it errors due to the fact that the new keys are not compliant JWT's.
Describe alternatives you've considered
Forgoing API use in favor of direct HTTP calls
Continuing to use anon and service_role keys (marked for deprecation at an indeterminate point in the future)
Feature request
Supabase has made clear their intent to migrate customers to the new Publishable and Secret API Keys. To maintain functionality moving forward, the ability for this package to use those keys is important
Describe the solution you'd like
Ability to authenticate Client.Auth, Client.AdminAuth, etc, with the Publishable or Secret keys instead of the anon or service role keys. Currently, if you simply try to pass the API keys in, it errors due to the fact that the new keys are not compliant JWT's.
Describe alternatives you've considered
Forgoing API use in favor of direct HTTP calls
Continuing to use anon and service_role keys (marked for deprecation at an indeterminate point in the future)