# How to make Google Auth + supabase redirect to a private page

**URL:** <https://community.weweb.io/t/how-to-make-google-auth-supabase-redirect-to-a-private-page/4874>\
**Category:** Ask us anything\
**Tags:** authentication, supabase\
**Created:** [October 13, 2023, 9:33am UTC](https://community.weweb.io/t/how-to-make-google-auth-supabase-redirect-to-a-private-page/4874 "2023-10-13T09:33:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [October 13, 2023, 1:13pm UTC](https://community.weweb.io/t/how-to-make-google-auth-supabase-redirect-to-a-private-page/4874/2 "2023-10-13T13:13:00Z")

</div>

Hi @TapTap21 👋

Ah yes. I need to improve the docs on this!

You need to redirect to a public page because that’s what allows WeWeb (or any frontend for that matter) to read the cookie from the external provider before it gets the user:

 ![CleanShot 2023-10-13 at 15.07.17@2x](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/f/f3c0d8a8644b7b67a3553423cc9699d9ccfce9c1.jpeg)

If you redirected directly to a private page, the authentication would fail.

For your use case, your public page can be blank with a workflow triggered `On page load (before fetching collections)` to redirect the user to a private page:

 ![CleanShot 2023-10-13 at 15.11.55@2x](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/6/6644f5fe6b1d86df0876f6d16ee0683b9a711b33.png)

Here’s the replay of [a live stream we did on the topic of OAuth](https://www.youtube.com/live/FaTHPG9kUrk?si=-pceFBWYW1cONj36&t=1573) in case you’re interested in learning more about the process 🙂

---

_[View the full topic](https://community.weweb.io/t/how-to-make-google-auth-supabase-redirect-to-a-private-page/4874)._