3
Realtime should allow user's jwt access token to connect from web client
Source: supabase/supabase#4086 · opened by @kk21
Hi,
When I used the user's jwt access token in web client's createClient() to subscribe to Realtime, I got repeated WebSocket connection failed errors.
However the subscription works using the anon or service key in createClient().
Using the anon key in createClient() and then setAuth(user's jwt) also works.
I wonder if using the user's jwt directly in createClient() should work so that the web client does not need the anon key?
Thanks.
When I used the user's jwt access token in web client's createClient() to subscribe to Realtime, I got repeated WebSocket connection failed errors.
However the subscription works using the anon or service key in createClient().
Using the anon key in createClient() and then setAuth(user's jwt) also works.
I wonder if using the user's jwt directly in createClient() should work so that the web client does not need the anon key?
Thanks.
No pledges yet. Be the first to back this.
Comments
Similar requests
Changing JWTs to RS256 to verify JWT inside getSession() anywhere
4 votes · 0 comments
Why do I need to do manual refresh of the realtime token?
1 vote · 0 comments
Email Verification API support with SD-JWT for native email verification
2 votes · 0 comments
Make Changes to the DB through a Realtime extension
2 votes · 0 comments
Authentication using API keys?
3 votes · 0 comments
No comments yet.