2
Include OIDC compliant JWT issuer like FusionAuth to Supabase Auth
Source: supabase/supabase#28762 · opened by @unknown
Bug report
• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the [Docs]( GitHub [Discussions]( and [Discord](
Describe the bug
Include [FusionAuth]( ass one of the third-party authentication providers.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
1. Go to
2. Try to add third-party provider other than Auth0, Firebase, or AWS Cognito.
Expected behavior
Expect to be able to give any third-party provider. I would expect that the same type of providers list that is accepted in (Auth.js)[ would be allowed for Supbase as long as the criteria is met for OIDC. There is an open [issue]( on this repo as well that I hope gets merged to make the oidc the default listing.
Screenshots
[ would be allowed for Supbase as long as the criteria is met for OIDC. There is an open [issue]( on this repo as well that I hope gets merged to make the oidc the default listing.
Screenshots
 anywhere
4 votes · 0 comments
Email Verification API support with SD-JWT for native email verification
2 votes · 0 comments
Request to Enable External JWT Authentication with Firebase (Project: dropnow-2025)
1 vote · 0 comments
Authentication using API keys?
3 votes · 0 comments
Ability to use any third party auth with asymmetric key
5 votes · 0 comments
No comments yet.