|
| 1 | +--- |
| 2 | +title: Microsoft Entra SSO integration with Directory Services Protector |
| 3 | +description: Learn how to configure single sign-on between Microsoft Entra ID and Directory Services Protector. |
| 4 | +services: active-directory |
| 5 | +author: jeevansd |
| 6 | +manager: CelesteDG |
| 7 | +ms.reviewer: CelesteDG |
| 8 | +ms.service: active-directory |
| 9 | +ms.subservice: saas-app-tutorial |
| 10 | +ms.workload: identity |
| 11 | +ms.topic: how-to |
| 12 | +ms.date: 10/03/2023 |
| 13 | +ms.author: jeedes |
| 14 | + |
| 15 | +--- |
| 16 | + |
| 17 | +# Microsoft Entra SSO integration with Directory Services Protector |
| 18 | + |
| 19 | +In this tutorial, you'll learn how to integrate Directory Services Protector with Microsoft Entra ID. When you integrate Directory Services Protector with Microsoft Entra ID, you can: |
| 20 | + |
| 21 | +* Control in Microsoft Entra ID who has access to Directory Services Protector. |
| 22 | +* Enable your users to be automatically signed-in to Directory Services Protector with their Microsoft Entra accounts. |
| 23 | +* Manage your accounts in one central location. |
| 24 | + |
| 25 | +## Prerequisites |
| 26 | + |
| 27 | +To integrate Microsoft Entra ID with Directory Services Protector, you need: |
| 28 | + |
| 29 | +* A Microsoft Entra subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/). |
| 30 | +* Directory Services Protector single sign-on (SSO) enabled subscription. |
| 31 | + |
| 32 | +## Scenario description |
| 33 | + |
| 34 | +In this tutorial, you configure and test Microsoft Entra SSO in a test environment. |
| 35 | + |
| 36 | +* Directory Services Protector supports both **SP and IDP** initiated SSO. |
| 37 | +* Directory Services Protector supports **Just In Time** user provisioning. |
| 38 | + |
| 39 | +## Adding Directory Services Protector from the gallery |
| 40 | + |
| 41 | +To configure the integration of Directory Services Protector into Microsoft Entra ID, you need to add Directory Services Protector from the gallery to your list of managed SaaS apps. |
| 42 | + |
| 43 | +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator). |
| 44 | +1. Browse to **Identity** > **Applications** > **Enterprise applications** > **New application**. |
| 45 | +1. In the **Add from the gallery** section, type **Directory Services Protector** in the search box. |
| 46 | +1. Select **Directory Services Protector** from results panel and then add the app. Wait a few seconds while the app is added to your tenant. |
| 47 | + |
| 48 | +Alternatively, you can also use the [Enterprise App Configuration Wizard](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, and walk through the SSO configuration as well. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides) |
| 49 | + |
| 50 | +## Configure and test Microsoft Entra SSO for Directory Services Protector |
| 51 | + |
| 52 | +Configure and test Microsoft Entra SSO with Directory Services Protector using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between a Microsoft Entra user and the related user in Directory Services Protector. |
| 53 | + |
| 54 | +To configure and test Microsoft Entra SSO with Directory Services Protector, perform the following steps: |
| 55 | + |
| 56 | +1. **[Configure Microsoft Entra SSO](#configure-microsoft-entra-sso)** - to enable your users to use this feature. |
| 57 | + 1. **[Create a Microsoft Entra ID test user](#create-a-microsoft-entra-id-test-user)** - to test Microsoft Entra single sign-on with B.Simon. |
| 58 | + 1. **[Assign the Microsoft Entra ID test user](#assign-the-microsoft-entra-id-test-user)** - to enable B.Simon to use Microsoft Entra single sign-on. |
| 59 | +1. **[Configure Directory Services Protector SSO](#configure-directory-services-protector-sso)** - to configure the single sign-on settings on application side. |
| 60 | + 1. **[Create Directory Services Protector test user](#create-directory-services-protector-test-user)** - to have a counterpart of B.Simon in Directory Services Protector that is linked to the Microsoft Entra ID representation of user. |
| 61 | +1. **[Test SSO](#test-sso)** - to verify whether the configuration works. |
| 62 | + |
| 63 | +## Configure Microsoft Entra SSO |
| 64 | + |
| 65 | +Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin center. |
| 66 | + |
| 67 | +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator). |
| 68 | +1. Browse to **Identity** > **Applications** > **Enterprise applications** > **Directory Services Protector** > **Single sign-on**. |
| 69 | +1. On the **Select a single sign-on method** page, select **SAML**. |
| 70 | +1. On the **Set up single sign-on with SAML** page, click the pencil icon for **Basic SAML Configuration** to edit the settings. |
| 71 | + |
| 72 | +  |
| 73 | + |
| 74 | +1. On the **Basic SAML Configuration** section, if you have **Service Provider metadata file**, perform the following steps: |
| 75 | + |
| 76 | + a. Click **Upload metadata file**. |
| 77 | + |
| 78 | +  |
| 79 | + |
| 80 | + b. Click on **folder logo** to select the metadata file and click **Upload**. |
| 81 | + |
| 82 | +  |
| 83 | + |
| 84 | + c. After the metadata file is successfully uploaded, the **Identifier** and **Reply URL** values get auto populated in Basic SAML Configuration section. |
| 85 | + |
| 86 | +  |
| 87 | + |
| 88 | + > [!Note] |
| 89 | + > If the **Identifier** and **Reply URL** values do not get auto populated, then fill in the values manually according to your requirement. |
| 90 | + |
| 91 | +1. Perform the following step, if you wish to configure the application in **SP** initiated mode: |
| 92 | + |
| 93 | + In the **Sign on URL** text box, type a URL using the following pattern: |
| 94 | + `https://<HOSTNAME>.<DOMAIN>.<EXTENSION>/DSP/Login/SsoLogin` |
| 95 | + |
| 96 | + > [!NOTE] |
| 97 | + > The Sign on URL value is not real. Update this value with the actual Sign on URL. Contact [Directory Services Protector support team](mailto:[email protected]) to get this value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Microsoft Entra admin center. |
| 98 | + |
| 99 | +1. Directory Services Protector support team application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes. |
| 100 | + |
| 101 | +  |
| 102 | + |
| 103 | +1. In addition to above, Directory Services Protector support team application expects few more attributes to be passed back in SAML response, which are shown below. These attributes are also pre populated but you can review them as per your requirements. |
| 104 | + |
| 105 | + | Name | Source Attribute| |
| 106 | + | ---------------| --------- | |
| 107 | + | role | user.assignedroles | |
| 108 | + |
| 109 | + > [!NOTE] |
| 110 | + > Please click [here](../develop/howto-add-app-roles-in-azure-ad-apps.md#app-roles-ui) to know how to configure Role in Microsoft Entra ID. |
| 111 | +
|
| 112 | +1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer. |
| 113 | + |
| 114 | +  |
| 115 | + |
| 116 | +1. On the **Set up Directory Services Protector** section, copy the appropriate URL(s) based on your requirement. |
| 117 | + |
| 118 | +  |
| 119 | + |
| 120 | +### Create a Microsoft Entra ID test user |
| 121 | + |
| 122 | +In this section, you'll create a test user in the Microsoft Entra admin center called B.Simon. |
| 123 | + |
| 124 | +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator). |
| 125 | +1. Browse to **Identity** > **Users** > **All users**. |
| 126 | +1. Select **New user** > **Create new user**, at the top of the screen. |
| 127 | +1. In the **User** properties, follow these steps: |
| 128 | + 1. In the **Display name** field, enter `B.Simon`. |
| 129 | + 1. In the **User principal name ** field, enter the [email protected]. For example, `[email protected]`. |
| 130 | + 1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box. |
| 131 | + 1. Select **Review + create**. |
| 132 | +1. Select **Create**. |
| 133 | + |
| 134 | +### Assign the Microsoft Entra ID test user |
| 135 | + |
| 136 | +In this section, you'll enable B.Simon to use Microsoft Entra single sign-on by granting access to Directory Services Protector. |
| 137 | + |
| 138 | +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator). |
| 139 | +1. Browse to **Identity** > **Applications** > **Enterprise applications** > **Directory Services Protector**. |
| 140 | +1. In the app's overview page, select **Users and groups**. |
| 141 | +1. Select **Add user/group**, then select **Users and groups** in the **Add Assignment** dialog. |
| 142 | + 1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen. |
| 143 | + 1. If you are expecting a role to be assigned to the users, you can select it from the **Select a role** dropdown. If no role has been set up for this app, you see "Default Access" role selected. |
| 144 | + 1. In the **Add Assignment** dialog, click the **Assign** button. |
| 145 | + |
| 146 | +## Configure Directory Services Protector SSO |
| 147 | + |
| 148 | +1. Log in to Directory Services Protector company site as an administrator. |
| 149 | + |
| 150 | +1. Go to **Settings (gear icon)** > **Data Connections** > |
| 151 | +**SAML Authentication** and toggle on the **Enabled** switch. |
| 152 | + |
| 153 | + |
| 154 | +1. In Step **1 - Identity provider**, select **Azure AD** from the drop-down menu and click **SAVE**. |
| 155 | + |
| 156 | +  |
| 157 | + |
| 158 | +1. In Step **2 – Data required by the SAML identity provider**, select **CONFIRM** button and **DOWNLOAD METADATA XML** to **Upload metadata file** in the **Basic SAML Configuration** section in Microsoft Entra admin center and click **SAVE**. |
| 159 | + |
| 160 | +  |
| 161 | + |
| 162 | +1. In Step **3 - User Attributes & Claims**, we don't need this information now, so we can skip to Step 4. |
| 163 | + |
| 164 | +1. In Step **4 – Data received from the SAML identity provider**, DSP supports both importing from a metadata URL and importing of a metadata XML provided by Entra ID. |
| 165 | + |
| 166 | + 1. Select **App federation metadata URL** radio button, and paste the **Metadata URL** in the field from Entra ID, and then select **IMPORT**. |
| 167 | + |
| 168 | +  |
| 169 | + |
| 170 | + 1. Select the radio button to use **Import federation metadata XML** and click **IMPORT XML** to upload the **Federation Metadata XML** file from Microsoft Entra admin center. |
| 171 | + |
| 172 | +  |
| 173 | + |
| 174 | + 1. Click **SAVE**. |
| 175 | + |
| 176 | +1. At the top of the **SAML Authentication** blade in DSP, it should show **Status** now as **Configured**. |
| 177 | + |
| 178 | +  |
| 179 | + |
| 180 | +### Create Directory Services Protector test user |
| 181 | + |
| 182 | +In this section, a user called Britta Simon is created in Directory Services Protector. Directory Services Protector supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in Directory Services Protector, a new one is created after authentication. |
| 183 | + |
| 184 | +## Test SSO |
| 185 | + |
| 186 | +In this section, you test your Microsoft Entra single sign-on configuration with following options. |
| 187 | + |
| 188 | +#### SP initiated: |
| 189 | + |
| 190 | +* Click on **Test this application** in Microsoft Entra admin center. This will redirect to Directory Services Protector Sign on URL where you can initiate the login flow. |
| 191 | + |
| 192 | +* Go to Directory Services Protector Sign on URL directly and initiate the login flow from there. |
| 193 | + |
| 194 | +#### IDP initiated: |
| 195 | + |
| 196 | +* Click on **Test this application** in Microsoft Entra admin center and you should be automatically signed in to the Directory Services Protector for which you set up the SSO. |
| 197 | + |
| 198 | +You can also use Microsoft My Apps to test the application in any mode. When you click the Directory Services Protector tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Directory Services Protector for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). |
| 199 | + |
| 200 | +## Next Steps |
| 201 | + |
| 202 | +Once you configure Directory Services Protector you can enforce session control, which protects exfiltration and infiltration of your organization's sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-any-app). |
0 commit comments