Azure Active Directory Connector Setup Guide

Overview

Reveal supports integration with Azure Active Directory to fetch Employee details into Reveal Hold. This document describes the prerequisites for integrating Reveal Hold with Azure AD.

Information Required for Integration

The following details are required for configuring the Azure Active Directory connector in Reveal Hold.

1. Client ID and Tenant ID of the registered application in Azure.

2. Client secret generated for the application.

The below sections describe the steps to be carried out to enable Azure Active Directory integration with Reveal Hold.

Register Application in Azure

Registering an application establishes a trust relationship between the app and the Microsoft identity platform. The trust is unidirectional: the app trusts the Microsoft identity platform, and not the other way around.

Follow the steps given below to create the app registration:

1. Sign in to the Azure portal.

2. If access to multiple tenants is available, from the top menu, use the Directory + subscription filter to select the tenant in which the application is to be registered.

3. Search for and select Azure Active Directory.

4. Under Manage, select App registrations > New registration.

5. Enter a Display Name for the application. Users of the application might see the display name when they use the app, for example, during sign-in. The display name can be changed at any time and multiple app registrations can share the same name. The app registration's automatically generated Application (client) ID, not its display name, uniquely identifies the app within the identity platform.

6. Specify Accounts in this organizational directory only can use the application. In some cases it is known as Sign-in audience.

7. Do not enter Redirect URI (optional). The following section describes how to configure a redirect URI.

8. Select Register to complete the initial app registration.

Add a Redirect URI

A redirect URI is the location where the Microsoft identity platform redirects a user's client and sends security tokens after authentication. In a production web application, for example, the redirect URI is often a public endpoint where the app is running.

Mobile and Desktop Applications

1. Select one of the suggested redirect URIs. For desktop applications using embedded browsers, https://login.microsoftonline.com/common/oauth2/nativeclient needs to be checked.

2. Select Configure to complete the platform configuration.

Add a Client Secret

The client secret is also known as an application password. It is a string value the app can use in place of a certificate to identify itself. The client secret is the easier of the two credential types to use.

To add a Client Secret, first select the application from App registrations in the Azure portal. Then follow the steps given below.

1. Select Certificates & secrets.

2. Select New client secret.

3. Add a Description and an Expiry for your client secret.

4. Select Add.

5. Record the secret's value for use in the client application code.

This secret value is never displayed again after leaving this page.

Add Permissions to Access Microsoft Graph

Configure delegated permission to Microsoft Graph to enable the client application to perform operations on behalf of the logged-in user, such as reading their email or modifying their profile. By default, users of the client app are asked, when they sign in, to consent to the delegated permissions configured for it.

To configure permissions,

1. Choose API permissions to view the options.

2. Select Add a permission > Microsoft Graph.

3. Select Delegated permissions. Microsoft Graph exposes many permissions, with the most commonly-used shown at the top of the list.

4. Under Select permissions, select the following permissions and navigate to Application Permissions, adjacent to Delegated permissions, to Select Application permissions listed in below table.