Hey! Someone that can help me set up Supabase Auth with Google in my Appsmith app? 😀

Hello @dreinon! This thread has been automatically created from your message in #843999948717555735 a ``few seconds ago``. Pinging @User so that they see this as well! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ... menu) and select Leave Thread to unsubscribe from future updates. Want to change the title? Use the

/title

command! We have solved your problem? Click the button below to archive it.

You are not likely to get much help on this unless you ask specific Supabase issues you are having or give some sample code you have tried. Don't know how many Appsmith users are here.

dreinon (2022-04-13)

@garyaustin right, what I don't really understand is the auth flow between the supabase gotrue rest api and the client in order to get authenticated. More specifically, what to do with the tokens that get attached to the hash when Google redirects to the redirect_uri specified. How can I use the access_token, refresh_token, etc

I'll be honest, I stick with the Supabase client code which deals with that, so don't mess with the details. Hopefully someone else jumps in with better info. But... Basically you use the jwt as a bearer token in the authorization header to access specific user data. The refresh token is used to get a new jwt before the expiration time, so you don't need to sign in again. https://github.com/supabase/gotrue#post-token talks about using the refresh token to get a new jwt (and refresh token for next time as it is marked "dead" when used).

Right, I wish I could use the supabase client in Appsmith but for now dependencies cannot be installed or used other than 4 libs they provide you

Well I can say the js client saves both in local storage. Your access token expires in an hour so you must refresh it before that if being used "live", or refresh it on startup with the refresh token if that time has passed. You then get a new access and refresh token.

The refresh token doesn't expire?

If a user signs out then all refresh tokens for that user are revoked. Users can sign in on multiple devices. The token is also revoked as soon as it used to get a jwt token.