3
Simple idea to sync client and server (cookie) access token
Source: supabase/supabase#6472 · opened by @fergusmeiklejohn
Using Remix, we also need to have the access token in a cookie so we can authenticate server side.
Problem: how to handle refreshing the token? The supabase client does so itself so perhaps the simplest solution is to allow us to pass a function to the function the supabase-js library is calling to refresh the access token? Then whenever the client refreshes we can call our api and update the access token on the cookie.
Problem: how to handle refreshing the token? The supabase client does so itself so perhaps the simplest solution is to allow us to pass a function to the function the supabase-js library is calling to refresh the access token? Then whenever the client refreshes we can call our api and update the access token on the cookie.
No pledges yet. Be the first to back this.
Comments
Similar requests
Ability To Reduce Cookie Size by Excluding Metadata
11 votes · 0 comments
PAT security vulnerability for MCP - prod access
2 votes · 0 comments
Enable Supabase SSR cookies with Vike Cloudflare
1 vote · 0 comments
Forcefully create a managed user session.
1 vote · 0 comments
Why do I need to do manual refresh of the realtime token?
1 vote · 0 comments
No comments yet.