Google one tap with supabase plugin

Ask us anything
1

Hi all,

I’m trying to implement Google One Tap alongside WeWeb’s Supabase Auth plugin. While I can successfully authenticate users with Google One Tap and create valid Supabase sessions, I’m not sure how to get them within the Supabase x WeWeb authentication framework.

I understand that WeWeb’s Supabase Auth plugin handles authentication state in a specific way, where user session data is stored and managed within WeWeb’s authentication framework rather than just relying on localStorage (correct me if I am wrong).

My questions are:

  1. Does WeWeb’s Google OAuth integration currently support Google One Tap functionality?
  2. If not, is there a way to integrate a custom Google One Tap implementation with WeWeb’s Supabase Auth plugin?
  3. How exactly does the Supabase Auth plugin store and manage user sessions? Is there a specific format or method I should follow to ensure WeWeb recognizes sessions created outside its own authentication workflow?

I’ve implemented Google One Tap that successfully authenticates with Supabase (I can see the user and session in Supabase), but how can I make WeWeb recognize the authenticated state when redirecting?

2

Hi @Tims

Following our conversation in the chat support, let us know if you were able to implement this with wwLib.wwPlugins.supabase.instance; :slight_smile:

3

Hey @DanielL!

Yes that fixed it, thank you so much