Storing Google OAuth Tokens
The docs say to securely store tokens:
https://supabase.com/docs/guides/auth/social-login/auth-google?queryGroups=environment&environment=client#saving-google-tokens
but don't explain how.
What's the recommended way of doing this?
So far, sign in w/ supabase auth + google oauth is working well and i can use the tokens to access api functionality but I need to store them else i have to relogin everytime. (This is a next.js project w/ supabase auth and DB btw)
From my understanding and research the two ways to do this securely are through browser in-memory storage or saving encrypted tokens to the database and linking them user. I'm not sure this is correct though.
Are there any docs/examples/guides on how to store these tokens safely and correctly? Would love to know I'm implementing everything as intended and if theres a choice I need to make (and the tradeoffs between them).
Would love to have an official method added to the docs so I know what the suggested best practice way is!
https://supabase.com/docs/guides/auth/social-login/auth-google?queryGroups=environment&environment=client#saving-google-tokens
but don't explain how.
What's the recommended way of doing this?
So far, sign in w/ supabase auth + google oauth is working well and i can use the tokens to access api functionality but I need to store them else i have to relogin everytime. (This is a next.js project w/ supabase auth and DB btw)
From my understanding and research the two ways to do this securely are through browser in-memory storage or saving encrypted tokens to the database and linking them user. I'm not sure this is correct though.
Are there any docs/examples/guides on how to store these tokens safely and correctly? Would love to know I'm implementing everything as intended and if theres a choice I need to make (and the tradeoffs between them).
Would love to have an official method added to the docs so I know what the suggested best practice way is!
