Continue to custom.domain instead of XXXX.supabase.co when using Google as provider #5041
|
When users log in with Google, they see the modal "Continue to "asdasdasdad.supabase.co", which looks not trustworthy for users. I found two related issues, talking about URL rewrites, but by default, supabase redirects to "https://asdasdasdad.supabase.co/auth/v1/authorize". How do I change that? Related: |
Replies: 4 comments 11 replies
|
Hi @AdrianKrebs, there isn't a way to use custom domains for oauth logins for now, but we'll be looking to add custom domains soon (possibly Q2 or Q3 this year)! |
|
A client of mine says that their spam detector doesn't like the supabase.co stuff and that it's being problematic. I need this feature too. |
|
Did we get any update on this? It is pretty frustrating to use the Google process. Custom domain for auth should be part of supabase paying customers. |
|
Hey everyone, this is now possible by adding a custom domain to your Supabase project: https://supabase.com/docs/guides/platform/custom-domains You can also verify your app to display a custom name on the OAuth screen if you don't want to pay for the custom domain. |
Hey everyone, this is now possible by adding a custom domain to your Supabase project: https://supabase.com/docs/guides/platform/custom-domains
You can also verify your app to display a custom name on the OAuth screen if you don't want to pay for the custom domain.
https://support.google.com/cloud/answer/13463073?hl=en