sb-access-token,sb-refresh-token VS supabase-auth-token?
What is the difference between sb-access-token,sb-refresh-token AND supabase-auth-token?
I am building a chrome extension where I want users to login on the website. Currently, website sets cookie supabase-auth-token when logging in with email/password and it sets all 3 (sb-access-token,sb-refresh-token, supabase-auth-token) when logging in with Google.
My goal is to have extension use supabase-auth-token cookie (set by the website) and never sign out user unless user manually signs out from both extension and website. Is it possible to do so?
Right now, it seems like website refreshes supabase-auth-token periodically, keeping users forever signed in, which is expected. How can I accomplish same with extension?
I am building a chrome extension where I want users to login on the website. Currently, website sets cookie supabase-auth-token when logging in with email/password and it sets all 3 (sb-access-token,sb-refresh-token, supabase-auth-token) when logging in with Google.
My goal is to have extension use supabase-auth-token cookie (set by the website) and never sign out user unless user manually signs out from both extension and website. Is it possible to do so?
Right now, it seems like website refreshes supabase-auth-token periodically, keeping users forever signed in, which is expected. How can I accomplish same with extension?
