You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Experiencing issues with supabase.auth.signInWithIdToken via the react-native-fbsdk-next lib, custom auth flow, and web based approach for authentication. All errors point in the same direction:
ERROR : {"name":"AuthApiError","message":"Bad ID token","status":400}
In a separate scenario, follow the WebBrowser-based authentication approach.
Observe the errors in both methods.
Expected behavior
Successful authentication without errors using both the native and web approaches for logging in with Facebook credentials.
Screenshots
N/A
System information
N/A
Additional context
The issue seems related to handling JWT structures and server-side errors during the authentication process. Investigations into Supabase's handling of generic ID tokens and discussions on platforms like Reddit suggest this might be an upstream error with Supabase. Looking at the function ParseIDToken found at auth/internal/api/provider/oidc.go it looks like the same pattern needs to be applied to Facebook Id tokens.
Suggested fix
Add a new function parseFacebookIdToken to ParseIDToken that is specifically designed for FB JWT tokens.
The text was updated successfully, but these errors were encountered:
I'm also running into this trying to transition from Firebase auth to Supabase auth. It seems that Facebook auth is not usable with Supabase at the moment? This is a critical blocker for us. @hf@kangmingtay is this easily resolvable?
Bug Report
Describe the bug
Experiencing issues with
supabase.auth.signInWithIdToken
via thereact-native-fbsdk-next
lib, custom auth flow, and web based approach for authentication. All errors point in the same direction:ERROR : {"name":"AuthApiError","message":"Bad ID token","status":400}
To Reproduce
Steps to reproduce the behavior:
supabase.auth.signInWithIdToken
with react-native-fbsdk-next according to Supabase docs.Expected behavior
Successful authentication without errors using both the native and web approaches for logging in with Facebook credentials.
Screenshots
N/A
System information
N/A
Additional context
The issue seems related to handling JWT structures and server-side errors during the authentication process. Investigations into Supabase's handling of generic ID tokens and discussions on platforms like Reddit suggest this might be an upstream error with Supabase. Looking at the function
ParseIDToken
found at auth/internal/api/provider/oidc.go it looks like the same pattern needs to be applied to Facebook Id tokens.Suggested fix
Add a new function
parseFacebookIdToken
toParseIDToken
that is specifically designed for FB JWT tokens.The text was updated successfully, but these errors were encountered: