|
| 1 | +--- |
| 2 | +title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with Fortes Change Cloud | Microsoft Docs' |
| 3 | +description: Learn how to configure single sign-on between Azure Active Directory and Fortes Change Cloud. |
| 4 | +services: active-directory |
| 5 | +documentationCenter: na |
| 6 | +author: jeevansd |
| 7 | +manager: mtillman |
| 8 | +ms.reviewer: barbkess |
| 9 | + |
| 10 | +ms.assetid: 1590757f-ce9f-4066-911f-47f3d3b92443 |
| 11 | +ms.service: active-directory |
| 12 | +ms.subservice: saas-app-tutorial |
| 13 | +ms.workload: identity |
| 14 | +ms.tgt_pltfrm: na |
| 15 | +ms.topic: tutorial |
| 16 | +ms.date: 04/06/2020 |
| 17 | +ms.author: jeedes |
| 18 | + |
| 19 | +ms.collection: M365-identity-device-management |
| 20 | +--- |
| 21 | + |
| 22 | +# Tutorial: Azure Active Directory single sign-on (SSO) integration with Fortes Change Cloud |
| 23 | + |
| 24 | +In this tutorial, you'll learn how to integrate Fortes Change Cloud with Azure Active Directory (Azure AD). When you integrate Fortes Change Cloud with Azure AD, you can: |
| 25 | + |
| 26 | +* Control in Azure AD who has access to Fortes Change Cloud. |
| 27 | +* Enable your users to be automatically signed-in to Fortes Change Cloud with their Azure AD accounts. |
| 28 | +* Manage your accounts in one central location - the Azure portal. |
| 29 | + |
| 30 | +To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on). |
| 31 | + |
| 32 | +## Prerequisites |
| 33 | + |
| 34 | +To get started, you need the following items: |
| 35 | + |
| 36 | +* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/). |
| 37 | +* Fortes Change Cloud single sign-on (SSO) enabled subscription. |
| 38 | + |
| 39 | +## Scenario description |
| 40 | + |
| 41 | +In this tutorial, you configure and test Azure AD SSO in a test environment. |
| 42 | + |
| 43 | +* Fortes Change Cloud supports **SP and IDP** initiated SSO |
| 44 | +* Once you configure Fortes Change Cloud you can enforce session control, which protect exfiltration and infiltration of your organization’s sensitive data in real-time. Session control extend from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/proxy-deployment-any-app). |
| 45 | + |
| 46 | +## Adding Fortes Change Cloud from the gallery |
| 47 | + |
| 48 | +To configure the integration of Fortes Change Cloud into Azure AD, you need to add Fortes Change Cloud from the gallery to your list of managed SaaS apps. |
| 49 | + |
| 50 | +1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account. |
| 51 | +1. On the left navigation pane, select the **Azure Active Directory** service. |
| 52 | +1. Navigate to **Enterprise Applications** and then select **All Applications**. |
| 53 | +1. To add new application, select **New application**. |
| 54 | +1. In the **Add from the gallery** section, type **Fortes Change Cloud** in the search box. |
| 55 | +1. Select **Fortes Change Cloud** from results panel and then add the app. Wait a few seconds while the app is added to your tenant. |
| 56 | + |
| 57 | + |
| 58 | +## Configure and test Azure AD single sign-on for Fortes Change Cloud |
| 59 | + |
| 60 | +Configure and test Azure AD SSO with Fortes Change Cloud using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Fortes Change Cloud. |
| 61 | + |
| 62 | +To configure and test Azure AD SSO with Fortes Change Cloud, complete the following building blocks: |
| 63 | + |
| 64 | +1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature. |
| 65 | + 1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon. |
| 66 | + 1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on. |
| 67 | +1. **[Configure Fortes Change Cloud SSO](#configure-fortes-change-cloud-sso)** - to configure the single sign-on settings on application side. |
| 68 | + 1. **[Create Fortes Change Cloud test user](#create-fortes-change-cloud-test-user)** - to have a counterpart of B.Simon in Fortes Change Cloud that is linked to the Azure AD representation of user. |
| 69 | +1. **[Test SSO](#test-sso)** - to verify whether the configuration works. |
| 70 | + |
| 71 | +## Configure Azure AD SSO |
| 72 | + |
| 73 | +Follow these steps to enable Azure AD SSO in the Azure portal. |
| 74 | + |
| 75 | +1. In the [Azure portal](https://portal.azure.com/), on the **Fortes Change Cloud** application integration page, find the **Manage** section and select **single sign-on**. |
| 76 | +1. On the **Select a single sign-on method** page, select **SAML**. |
| 77 | +1. On the **Set up single sign-on with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings. |
| 78 | + |
| 79 | +  |
| 80 | + |
| 81 | +1. On the **Basic SAML Configuration** section, if you wish to configure the application in **IDP** initiated mode, enter the values for the following fields: |
| 82 | + |
| 83 | + a. In the **Identifier** text box, type a URL using the following pattern: |
| 84 | + `https://<identifier>.fortes-online.com` |
| 85 | + |
| 86 | + b. In the **Reply URL** text box, type a URL using the following pattern: |
| 87 | + `https://<identifier>.fortes-online.com/saml/SSO` |
| 88 | + |
| 89 | +1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode: |
| 90 | + |
| 91 | + In the **Sign-on URL** text box, type a URL using the following pattern: |
| 92 | + `https://<identifier>.fortes-online.com/saml/SSO` |
| 93 | + |
| 94 | + > [!NOTE] |
| 95 | + > These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [Fortes Change Cloud Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal. |
| 96 | + |
| 97 | +1. Fortes Change Cloud 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, where as **nameidentifier** is mapped with **user.userprincipalname**. Fortes Change Cloud application expects **nameidentifier** to be mapped with **user.samaccountname**, so you need to edit the attribute mapping by clicking on **Edit** icon and change the attribute mapping. |
| 98 | + |
| 99 | +  |
| 100 | + |
| 101 | +1. On the **Set up single sign-on with SAML** page, In the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer. |
| 102 | + |
| 103 | +  |
| 104 | + |
| 105 | +### Create an Azure AD test user |
| 106 | + |
| 107 | +In this section, you'll create a test user in the Azure portal called B.Simon. |
| 108 | + |
| 109 | +1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**. |
| 110 | +1. Select **New user** at the top of the screen. |
| 111 | +1. In the **User** properties, follow these steps: |
| 112 | + 1. In the **Name** field, enter `B.Simon`. |
| 113 | + 1. In the **User name ** field, enter the [email protected]. For example, `[email protected]`. |
| 114 | + 1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box. |
| 115 | + 1. Click **Create**. |
| 116 | + |
| 117 | +### Assign the Azure AD test user |
| 118 | + |
| 119 | +In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Fortes Change Cloud. |
| 120 | + |
| 121 | +1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**. |
| 122 | +1. In the applications list, select **Fortes Change Cloud**. |
| 123 | +1. In the app's overview page, find the **Manage** section and select **Users and groups**. |
| 124 | + |
| 125 | +  |
| 126 | + |
| 127 | +1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog. |
| 128 | + |
| 129 | +  |
| 130 | + |
| 131 | +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. |
| 132 | +1. If you're expecting any role value in the SAML assertion, in the **Select Role** dialog, select the appropriate role for the user from the list and then click the **Select** button at the bottom of the screen. |
| 133 | +1. In the **Add Assignment** dialog, click the **Assign** button. |
| 134 | + |
| 135 | +## Configure Fortes Change Cloud SSO |
| 136 | + |
| 137 | +To configure single sign-on on **Fortes Change Cloud ** side, you need to send the **App Federation Metadata Url ** to [Fortes Change Cloud support team ](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides. |
| 138 | + |
| 139 | +### Create Fortes Change Cloud test user |
| 140 | + |
| 141 | +In this section, you create a user called Britta Simon in Fortes Change Cloud. Work with [Fortes Change Cloud support team ](mailto:[email protected]) to add the users in the Fortes Change Cloud platform. Users must be created and activated before you use single sign-on. |
| 142 | + |
| 143 | +## Test SSO |
| 144 | + |
| 145 | +In this section, you test your Azure AD single sign-on configuration using the Access Panel. |
| 146 | + |
| 147 | +When you click the Fortes Change Cloud tile in the Access Panel, you should be automatically signed in to the Fortes Change Cloud for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction). |
| 148 | + |
| 149 | +## Additional resources |
| 150 | + |
| 151 | +- [ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list) |
| 152 | + |
| 153 | +- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis) |
| 154 | + |
| 155 | +- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview) |
| 156 | + |
| 157 | +- [Try Fortes Change Cloud with Azure AD](https://aad.portal.azure.com/) |
| 158 | + |
| 159 | +- [What is session control in Microsoft Cloud App Security?](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad) |
| 160 | + |
| 161 | +- [How to protect Fortes Change Cloud with advanced visibility and controls](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad) |
| 162 | + |
0 commit comments