Google OAuth & OpenID connect Single Sign-On (SSO) | Google SSO Login

Step 1: Setup Google as OAuth Provider

• Go to https://console.developers.google.com/ and sign up/login.
• Click on Select Project to create a new Google Apps Project,you will see a popup with the list of all your projects.

• You can click on the New project button to create new project.

• Enter your Project name under the Project Name field and click on Create.

• Go to Navigation MenuAPIsServicesCredentials.

• Click on Create Credentials button and then select OAuth Client ID from the options provided.

• In case you are facing some warning saying that in order to create an OAuth Client ID, you must set a product name on consent screen (as shown in below image). Click on the Configure consent screen button.

• Enter the required details such as App Name, User Support Email. and click on Save and Continue button.

• Now for configuring scopes, click on Add or Remove the Scopes button.

• Now, Select the Scopes to allow your project to access specific types of private user data from their Google Account and click on Save and Continue button.

• Go to the Credentials tab and click on Create Credentials button. Select Web Application from dropdown list to create new application.

• Enter the name you want for your Client ID under the name field and enter the Redirect/Callback URI from miniOrange OAuth Client plugin/module under the Authorized redirect URIs field and click on Create button.

• You will see a popup with the Client ID and Client Secret Copy your Client ID and Client Secret and save it on your miniOrange OAuth Client plugin Configuration.

• You have successfully completed your Google App OAuth Server side configurations.



Google Endpoints and Scope:




Client ID :	Click Here
Client Secret :	Click Here
Scope:	Openid email Profile
Authorize Endpoint:	https://accounts.google.com/o/oauth2/auth
Access Token Endpoint:	https://www.googleapis.com/oauth2/v4/token
Get User Info Endpoint:	https://www.googleapis.com/oauth2/v1/userinfo

You have successfully configured Google as OAuth Provider for achieving Google login into your WordPress Site.

Step 2: Setup WordPress as OAuth Client

• Go to Configure OAuth tab and Select Google from the OAuth Providers list. Then, configure App Name, Client ID, Client Secret, Scope from provided Endpoints.
• Click on Save Settings to save the configuration.

You have successfully configured WordPress as OAuth Client for achieving Google login into your WordPress Site.

Step 3: User Attribute Mapping.

• User Attribute Mapping is mandatory for enabling users to successfully login into WordPress. We will be setting up user profile attributes for WordPress using below settings.

Finding user attributes

• Go to Configure OAuth tab. Scroll down and click on Test Configuration.

• You will see all the values returned by your OAuth Provider to WordPress in a table. If you don't see value for First Name, Last Name, Email or Username, make the required settings in your OAuth Provider to return this information.

• Once you see all the values in Test Configuration, go to Attribute / Role Mapping tab, you will get the list of attributes in a Username dropdown.

Step 4: Login Settings / Sign In Settings.

• The settings in SSO Settings tab define the user experience for Single Sign-On . To add a login widget on your WordPress page, you need to follow below steps.

Sign In Settings

• Go to WordPress Left Panel > Appearances > Widgets.
• Select miniOrange OAuth. Drag and drop to your favourite location and save.

• Open your WordPress page and you can see the login button there. You can test the SSO now.

In this Guide, you have successfully configure Google Single Sign-On (SSO) by configuring Google as OAuth Provider and WordPress as OAuth Client using our WP OAuth Single Sign-On ( OAuth & OpenID Connect Client ) plugin. This solution ensures that you are ready to roll out secure access to your WordPress site using Google login credentials within minutes.

Additional Resources

• What is OAuth 2.0?
• Access Google API' s using Oauth 2.0
• Frequently Asked Questions (FAQs)