5
Ability to use any third party auth with asymmetric key
Source: supabase/supabase#32775 · opened by @jbojcic1
Right now when you want to use Supabase with some third party auth you have two options:
1. If your third party auth is Firebase or Auth0 or AWS Cognito you can use this approach
2. Create your own jwt and sign it with jwt secret from the Supabase dashboard.
Option 2 is very cumbersome and adds unnecessary complexity. Option 1 works only for those providers but I don't see why it should not be possible to make it work for any provider that uses asymmetric key (pub/priv key pair where jwt is signed with private key). Can't Supabase allow pasting public key of any auth provider in the settings instead which should be enough to validate the key?
1. If your third party auth is Firebase or Auth0 or AWS Cognito you can use this approach
2. Create your own jwt and sign it with jwt secret from the Supabase dashboard.
Option 2 is very cumbersome and adds unnecessary complexity. Option 1 works only for those providers but I don't see why it should not be possible to make it work for any provider that uses asymmetric key (pub/priv key pair where jwt is signed with private key). Can't Supabase allow pasting public key of any auth provider in the settings instead which should be enough to validate the key?
No pledges yet. Be the first to back this.
Comments
Similar requests
Asymmetric cryptography
3 votes · 0 comments
Include OIDC compliant JWT issuer like FusionAuth to Supabase Auth
2 votes · 0 comments
Organization billing-read API for third-party OAuth apps
1 vote · 0 comments
Add Supabase to Atlassian Statuspage third-party component directory (statuspage.io - monitoring)
2 votes · 0 comments
Make Apple provider Secret Key optional for native-only Sign in with Apple
6 votes · 0 comments
No comments yet.