Google sign in with custom domain
I have setup a custom domain so that when a user signs into google, on the google page instead of seeing something like
continue to abcdefghijklmnopqrst.supabase.co, it shows continue to myapp.com
However when I then select my account to continue with, i get redirected to https://myapp.com/auth/v1/callback....... however this url does not exist it my app. Why doesnt it redirect to abcdefghijklmnopqrst.supabase.co/auth/v1/callback....?
Do I somehow have to map these urls to each other?10 Replies
Are you using this feature: https://supabase.com/docs/guides/platform/custom-domains for custom domains?
Custom Domains | Supabase Docs
Use a custom domain instead of the default Supabase domain for your project.
yes, i just saw that but the docs are confusing me a little. Not sure which part of those to look at
Did you pay for a custom domain?
yes i did
and what im most confused about is, google redirects to
myapp.com/auth/v1/callback which does not exist on my domain myapp.com. it needs to be the supabase url right?OK. Then those docs would apply. Some step is missing based on what you are saying. I don't have Pro and don't have that feature so can't help further. I was just making sure you were using that versus trying to roll your own thing.
The custom domain is for the supabase instance.
The auth/v1/callback is where the OAuth calls to confirm the user.
correct my its going to myapp.com/auth/v1/callback which does not exist, unless i have to mapp that to
abcdefghijklmnopqrst.supabase.co/auth/v1/callback
but not sure whereMaybe I'm wrong but I think that domain is where all the Supabase auth requsts will go and then the database requests can also go there or the standard instance name.
It is not your app domain.
I think that is why they show using api.myapp.com for the custom domain.
Your code is at myapp.com and the Supabase instance is at api.myapp.com
hmm