Set up SSO authentication with Azure AD#

#Objective

Do you have an Azure Active Directory in your company? If you want to use it to login to your Data Platform apps, this guide is for you.

Open the IAM and click on Auth. Provider.

If you haven't done so already, add a new Azure AD authentication provider. Else, just edit it.

The configuration is done in two parts. First you need to configure the rights on Microsoft Azure and then configure the authentication provider in the Data Platform Identity Access Manager.

#Configuration on Azure

You need to register Data Platform on the Azure console. Go there: https://portal.azure.com.

#Step 1. Retrieve the Tenant ID

The Tenant ID is the ID of your Azure company environment. To find it, select Azure Active Directory in the list of Azure Services. Then, in the sidebar click on "Properties".

#Step 2. Register the Identity Access Manager

You then need to register an application inside of Microsoft Azure AD. This works with any app you would like to connect to Azure but in this case, you are going to register the Data Platform IAM directly.

In the sidebar, select App Registrations. Then click on New registration.

#Name

The name is purely descriptive: it will be useful to find your configuration within your Azure AD.

#Supported account types

This parameter specifies which Azure AD directories you'll be able to use to authenticate on the Data Platform IAM. It is recommended to select Accounts in this organizational directory only in order that only your AD can log in to your Data Platform IAM.

#Redirect URL

Select Web.

In the URL field, copy and paste the Reply URL field in the new authentication provider you added on Data Platform (it is the same for the entire Data Platform IAM).

Once this is done, click on Register.

#Step 3. Retrieve the Client ID

The Client ID is the user ID of your newly added application (i.e. the Data Platform IAM). You can find it on its Overview page: look for Application (client) ID.

#Step 4. Retrieve the Client Secret

On the page of your IAM application, click on Certificates & secrets in the sidebar. Click on New client secret.

Fill in the description and expiration date of your choice and click on Add.

Once the client secret is created, copy and save its Value.

#Step 5. Enable basic permissions from Azure AD

On the page of your IAM application, click on API permissions in the sidebar. Click on New permission and select Microsoft Graph.

Select Delegated permissions.

Two permissions must be added in order for the entire feature-set of Azure AD authentication provider on Data Platform to work.

• profile: this permission is needed if you need to get user information from Azure AD using the UserInfo endpoint.
• Group.Read.All: this permission is needed if you need to get the list of groups from your Azure AD for a custom mapping

Find them in the list and add them both.

Finally, click on Grant admin consent for your-app and confirm.

When all permissions have been correctly added, your screen should look like this.

#Summary

If you have properly followed all the previous steps, you should have this list of information.

Tenant ID (Step 1): XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Client ID (Step 3): XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Client Secret (Step 4): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

#Configuration on the Data Platform Identity Access Manager

You now have to configure your new authentication provider in your Data Platform Identity Access Manager.

#Fill in the basic information

• Name / Description: This is the internal name and description for your new authentication method
• Directory: This is a unified tag for all accounts that will be created from this directory. For example, you can input Azure
• Tags: This offers more tagging options. They are completely optional
• Reply URL: This is the Data Platform URL where your authentication provider redirects to
• Active: This specifies whether this authentication provider can be used to login or not
• Debug Mode: When this is turned on, this enables you to see the authentication logs in the Control Center.

#Fill in Azure configuration

Now locate the Azure Configuration panel.

Fill in the information collected on Azure in the previous section, as such:

• Tenant ID: Tenant ID (retrieved in step 1 of the configuration on Azure)
• Client ID: Client ID (retrieved in step 3 of the configuration on Azure)
• Client Secret: Client Secret Value (retrieved in step 4 of the configuration on Azure)
• Scope: This represents how much information Data Platform will be able to access from your Azure AD. This field is optional: if left blank it will use the value openid email profile
• Enable user info endpoint on AzureAD: This endpoint will allow the IAM to do an extra GET https://graph.microsoft.com/v1.0/users/me call on Azure AD Graph API, the result of which will add a sub-object "user" in addition to the standard OpenID field in the response. This allows you to get additional information on users, like the job title.

#Bindings

The Bindings panel allows you to customize the mapping of the fields between Azure AD and Data Platform.

Email, login, first and last name are mapped by default.

Bindings can be overriden if you need to save additional information from Azure AD into your Data Platform Identity Access Manager, like the job title.

The easiest way to configure bindings is to retrieve a response from a login of an user by following these steps:

1 - Do a sample login to any Data Platform application using your newly configured Azure AD authentication provider.
2 - Open the Log History page of the IAM authentication provider (here Azure AD).

3 - Open the latest log: the original response from Azure AD will look like this:

{
  "aud": "3a0f2280-36e3-457b-a72a-d74fca8a0eae",
  "iss": "https://sts.windows.net/058c4703-07ad-4c14-87e5-e08241c8cb8f/",
  "iat": 1628084238,
  "nbf": 1628084238,
  "exp": 1628088138,
  "amr": [
    "pwd"
  ],
  "email": "test@example.com",
  "family_name": "Smith",
  "given_name": "John",
  "idp": "https://sts.windows.net/82b3359c-9391-4d7c-a0f2-816751a97641/",
  "ipaddr": "62.23.151.245",
  "name": "John Smith",
  "oid": "db6723ba-d536-4c72-bfb4-c089d88fe7d8",
  "rh": "0.ARAAA0eMBa0HFEyH5eCCQcjLj4AiDzrjNntFpyrXT8qKDq4QAOw.",
  "sub": "3H2vG1r81UmzHRIp74IHcYjONOSMZf4gQ12M_ELMorY",
  "tid": "058c4703-07ad-4c14-87e5-e08241c8cb8f",
  "unique_name": "test@example.com",
  "uti": "GO1KbxWFg0ChEVKPUDqhAA",
  "ver": "1.0",
  "memberships": [
    {
      "@odata.type": "#microsoft.graph.group",
      "id": "7d232d98-c942-4405-9380-a644b6db1eb7",
      ...
      "description": "TestGroup",
      "displayName": "My Group",
    },...
  ]
}

4 - On top of the default email, login, first and last name, any additional property from Azure AD can be saved as a custom configuration.XXX field on Data Platform by using the "JSON" mode.

For example, you can add a fullname property on Data Platform from the name field from Azure AD:

{
  "login": "email",
  "email": "email",
  "pronoun": "",
  "firstname": "given_name",
  "lastname": "family_name",
  "configuration.fullname": "name"
}

#Custom mappings

The Custom mappings panel allows you to automatically assign all users logged in through this authentication provider to a role or a group.

Learn how to set up custom mappings.

#Set live

You are all set configuring your Azure AD! If you haven't done it already, click on Create - else make sure to Save.

In the Authentication Providers list, you now see your new method. Make sure you set it as active.

Make sure this new authentication method is visible for the applications of your choice. You should now see an Azure AD option on your application's login page. By clicking on it, you will be redirected to the Azure login screen, or directly into the app if you are already logged into your account.

Make Azure AD visible on your apps' login page

#Go further

If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.

Ask questions, give your feedback and interact directly with the team building the Data Platform on the dedicated Discord channel.

If you need support with your OVHcloud services, create a request in our Help Centre.

Join our community of users.