Configure Google login for Discourse

[Discourse]

This guide explains how to set up Google login integration for your Discourse site by configuring OAuth2 credentials in the Google Cloud Console.

Required user level: Administrator

Overview

Google login allows users to sign in to your Discourse site using their Google accounts. This guide will walk you through:

1. Creating a Google Cloud project
2. Setting up OAuth consent
3. Configuring credentials
4. Enabling Google login in Discourse

Create a Google Cloud project

1. Navigate to https://console.developers.google.com
2. Click the project selection button in the top left
3. Click “New Project”

4. Enter a project name and optional location.
5. Click “Create”

If you see any errors after creating the project, refresh the page using Ctrl+F5.

Configure OAuth consent

1. Navigate back to https://console.developers.google.com and select your new project if it is not already slected.
2. Navigate to “OAuth consent screen” in the left panel. You can also use the top left Google Cloud menu to select “APIs & Services” → “Oauth consent screen”.

3. Click “Get Started”
4. Under “App Information” enter an app name and select a user-support email address.

5. Select “External” Audience

6. Next, enter a notifications email address
7. Finally, accept the API Services: User Data Policy and click “Create”

Set up credentials

1. Navigate to the "APIs & Services“ → "Credentials” screen
2. Click “Create Credentials” and select “OAuth Client ID”

3. Configure the OAuth client:

• Select “Web application” as the Application Type and give it a Name
• In Authorized JavaScript Origins, add your site’s base URL (including https://)
• Add your callback URL under Authorized Redirect URIs: https://your-discourse-site.com/auth/google_oauth2/callback
• Click “Create”

Click on the OAuth 2.0 Client ID:

Copy the ClientID and Client Secret to add to your Discourse admin:

Configure Discourse settings

1. In your Discourse admin settings under “Login & authentication”

• Enable the setting enable google oauth2 logins
• Enter your google oauth2 client id
• Enter your google oauth2 client secret

Verify and publish

Test the integration by adding a user with a Google email address and confirming you can log in to Discourse using the “Log in with Google” option. If you are able to log in then the configuration is complete!

NOTE:

Previously there was one final step required - changing the Google Developer Project to production status. This no longer appears to be required. We are leaving these legacy notes here just in case.

To make the integration publicly available:

• Change the status to “In production”-
• Complete Google’s verification process
• Verify site ownership through Google Search Console

Additional configuration

Google Workspace (formally G. Suite, Google Apps) login

To restrict login to specific Google Workspace domains:

1. In Discourse Admin -> Login & authentication, locate the google oauth2 hd site setting
2. Enter your Google Workspace domain

Troubleshooting

If you experience login issues:

• Verify that HTTPS is properly configured
• Double-check all redirect URIs
• Ensure your site’s SSL certificate is valid
• Confirm that all required Google Cloud APIs are enabled

Related resources

• Using OAuth 2.0 for Web Server Applications  |  Authorization  |  Google for Developers
• Perform Google Search Console Verification with Discourse

Last edited by @Southpaw 2025-03-11T02:06:51Z

Check document

Perform check on document:

[Deenius (Daniel Jurnik)]

Unfortunately, if I follow the instructions, the login does not work.

In order to get the login to work, I had to add both URL formats for redirection.

https://forum.example.com//auth/google_oauth2/callback http:///forum.example.comauth/google_oauth2/callback

However, I am now unable to submit the app for publication because Google only requires addresses in the HTTPS format.

Any advice on how to solve this?

[pfaffman (Jay Pfaffman)]

I guess you don’t have a standard install and need to turn on force_https.

[Deenius (Daniel Jurnik)]

I followed the official installation. Force HTTPS is enabled.

EDIT: It’s weird, but now it’s started to work! I tried it at least ten times before, but it didn’t work.

I can’t explain it because the procedure was exactly the same. Maybe something on Google’s side?

[pfaffman (Jay Pfaffman)]

It makes no sense that it’d be accessing google with http.