Google Apps OAuth Single Sign-On (SSO) into TYPO3 | TYPO3 Google OAuth Login

Typo3 OAuth 2.0 Authentication and Authorization Single Sign-On (SSO) extension allows your Frontend & Backend (Admin & Customer) users to seamlessly login into Typo3 site using Google Apps credentials. The Typo3 OAuth / OpenID Connect Single Sign-On (SSO) extension makes it easy to use OAuth2 to set up Google Apps Login on Typo3 (Google Apps Single Sign on).

The Typo3 OAuth & OpenID Connect Single Sign-On (SSO) extension makes it possible to log into Typo3 securely using any OAuth and OpenID Connect provider such as Azure AD, Azure B2C, Okta, Keycloak, Salesforce etc. Advanced Single Sign-On (SSO) features such as user profile Attribute Mapping, Role Mapping, and so on are also supported in this extension. Click here to read more about the Typo3 OAuth Single Sign-On (OAuth & OpenID Connect Client) extensions's premium features.

In this guide, We'll go over how to set up SSO between Typo3 and Google Apps. Users should be able to log in to Typo3 through Google Apps by the end of this guide.

Steps to configure Google Apps OAuth & OpenID Single Sign-On (SSO) Login into Typo3

1. Setup Google Apps as OAuth Provider

Follow the steps below to configure Google Apps as OAuth Provider

 Configure Google Apps 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 for Typo3 OAuth Client, you will see a popup with the list of all your projects.

• Click on the New project button to create new project.

• Enter your Project Name in 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 the dropdown menu.

• Choose how you want to configure and register your app (User Type) and click on create button.

• 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.

• Fill up the required information, such as the App Name and User Support Email. and then select the Save and Continue option.

• 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 Typo3 OAuth and OpenID Single Sign On (SSO) plugin 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 Typo3 OAuth and OpenID Single Sign On (SSO) plugin Configuration.

You have successfully configured Google Apps as OAuth Provider for achieving Google Apps Single Sign-On (SSO) with Typo3 for user authentication.

2. Configuring Typo3 as OAuth Client

• After successfully configuring OAuth Provider, enter the OAuth Provider Name, Client ID, Client Secret, Scope and provided endpoints.
  
  

  Please refer below Endpoints to configure the OAuth client

  
  

  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

• Click on the Save button to save the settings.

• Click on the Test Configuration button.

• You will see all the values returned by your OAuth Provider to Typo3 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.
• You have successfully configured your Typo3 as an OAuth Client. Now you can create your custom SSO button in your Typo3 Frontend site and embed the FEOIDC page URL to it to initiate the SSO.

3: Attribute Mapping (Optional). *This is Premium feature.

• You can map attributes in the Attribute Mapping tab. Only username and email are allowed to be mapped in free version of the extension. However, in the premium version of the extension, you can map various attributes coming from your OAuth Provider to the attributes present in your Typo3 site.

4: Group Mapping (Optional). *This is Premium feature.

• You can specify a default role in the free extension that will be allocated to all non-admin users when they conduct SSO.
• Go to Group mapping tab and navigate to Group Mapping section.
• Select the Default Role and click on the Save button.

By configuring Google Apps as an OAuth Provider and Typo3 as an OAuth Client using our Typo3 OAuth Client extension, you have successfully installed Typo3 Google Apps Single Sign-On (SSO). Within minutes, you'll be able to provide safe access to your Typo3 site utilising Google Apps login credentials thanks to this solution.

Additional Resources

• What is Single Sign-On (SSO) Login?
• What is OAuth 2.0?
• How OAuth works?
• Typo3 OAuth and OpenID Single Sign On (SSO) Extension.
• Typo3 SAML Single Sign On (SSO) Extension.

If you are looking for anything which you cannot find, please drop us an email on info@xecurify.com