Skip to content

Commit a63e912

Browse files
Update the docs for domains on google oAuth screens (supabase#37942)
* Update the docs for google domains. * Apply suggestion from @ChrisChinchilla Co-authored-by: Chris Chinchilla <[email protected]> * Apply suggestion from @ChrisChinchilla Co-authored-by: Chris Chinchilla <[email protected]> --------- Co-authored-by: Chris Chinchilla <[email protected]>
1 parent afd82d1 commit a63e912

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

apps/docs/content/guides/auth/social-login/auth-google.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -801,4 +801,5 @@ chrome.identity.launchWebAuthFlow(
801801

802802
By default, the Google consent screen shows the root domain of the callback URL, where Google will send the authentication response. With Supabase Auth, it is your Supabase project's domain `(https://<your-project-ref>.supabase.co)`.
803803

804-
If that is not preferable, you can use a [Custom Domain](https://supabase.com/docs/guides/platform/custom-domains) with your Supabase project. You can use it as your project's domain when creating the Supabase client in your application and initiating the authentication flow. It will then show up in the Google consent screen. If you want your app name and the logo on the consent screen, [you must submit your app to Google for verification](https://support.google.com/cloud/answer/10311615).
804+
You can change this domain in the settings for your Google app. Go to Google App Platform, click on Branding, and then set your application home page, privacy policy, and terms of use. You can also add your logo.
805+
Next, go to Audience and click publish. Google will need to verify the app, which usually takes around 24 hours.

0 commit comments

Comments
 (0)