Integration of Azure AD Login (Azure Active Directory OAuth Single Sign-On) with Typo3 using OAuth 2.0 Protocol. The Typo3 OAuth / OpenID Connect Single Sign-On (SSO) extension makes it easy to use OAuth2 to set up Azure AD Login on Typo3 (Azure AD Single Sign on).

The extension can be set up using other Social Media sources, as well as custom OAuth and OIDC providers. It contains a lot of Single Sign-On (SSO) features, like Attribute Mapping for user profiles, Role Mapping, and so on. In this guide, we'll go over how to set up SSO between Typo3 and Azure AD. At the end of this article, users should be able to log into Typo3 using Azure AD. Click here to read more about the Typo3 OAuth Single Sign-On (OAuth & OpenID Connect Client) extensions extra features.

The Typo3 OAuth & OpenID Connect Single Sign-On (SSO) extension makes it possible to log into Typo3 securely using Azure AD as an OAuth and OpenID Connect provider. You can also use alternative OAuth providers, such as Azure B2C, Office 365, and other custom providers, to configure the plugin. Advanced Single Sign-On features such as user profile Attribute Mapping, Role Mapping, and so on are supported. We'll go over how to set up SSO between Typo3 and Azure AD in this article. Users should be able to log in to Typo3 through Azure AD by the end of this guide.

Click here to know more about other features we provide in Typo3 OAuth Single Sign-On ( OAuth & OpenID Connect Client ) extension

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

1. Setup Azure AD as OAuth Provider

Follow the steps below to configure Azure AD as OAuth Provider

 Configure Azure AD as OAuth Provider

• Sign in to Azure portal.
• Select Azure Active Directory.

• In the left-hand navigation pane, click the App registrations service, and click New registration.

• When the Create page appears, enter your application's registration information.(Refer to the below table)

Name :	Name of your application.
Application type :	Select "Web app / API" for client applications and resource/API applications that are installed on a secure server. This setting is used for OAuth confidential web clients and public user-agent-based clients. The same application can also expose both a client and resource/API.
Redirect URI :	For "Web app / API" applications, provide the base URL of your app. eg, https://<domain-name> might be the URL for a web app running on your local machine. Users would use this URL to sign in to a web client application.

• Copy Callback URL from the miniOrange OAuth Client extension and save it under the Redirect URL textbox.

• Make sure the "Grant admin consent to openid and offline_access permissions" option is enabled. When finished, click Register.

• Azure AD assigns a unique Application ID to your application. The Application ID is your Client ID and the Directory ID is your Tenant ID, keep these values handy as you will need them to configure the miniOrange OAuth Client extension.

• Go to Certificates and Secrets from the left navigaton pane and click on New Client Secret. Enter description and expiration time and click on ADD option.

• Copy the secret key "value" and keep the value handy it will be required later to configure Client Secret under the miniOrange OAuth Client extension.

You have successfully configured Azure AD as OAuth Provider for achieving Azure AD 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
  Authorize Endpoint:	https://login.microsoftonline.com/[tenant-id]/oauth2/v2.0/authorize
  Access Token Endpoint:	https://login.microsoftonline.com/[tenant-id]/oauth2/v2.0/token
  Get User Info Endpoint:	https://graph.microsoft.com/beta/me

• 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. You will see the SSO button on your frontend. Click on the button and test 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 Azure AD as an OAuth Provider and Typo3 as an OAuth Client using our Typo3 OAuth Client extension, you have successfully installed Typo3 Azure AD Single Sign-On (SSO). Within minutes, you'll be able to provide safe access to your Typo3 site utilising Azure AD login credentials thanks to this solution.

Additional Resources

• What is Single Sign-On (SSO) Login?
• Azure AD SSO | Azure Single Sign-On (SSO) Login
• Azure AD - Overview
• What is OAuth 2.0?
• How OAuth works?
• Azure AD - What is Azure Active Directory?

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