|
| 1 | +--- |
| 2 | +title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with WEDO | Microsoft Docs' |
| 3 | +description: Learn how to configure single sign-on between Azure Active Directory and WEDO. |
| 4 | +services: active-directory |
| 5 | +documentationCenter: na |
| 6 | +author: jeevansd |
| 7 | +manager: mtillman |
| 8 | +ms.reviewer: barbkess |
| 9 | + |
| 10 | +ms.assetid: 73adc94e-7656-4a92-99e3-a401c67be477 |
| 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: 01/22/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 WEDO |
| 23 | + |
| 24 | +In this tutorial, you'll learn how to integrate WEDO with Azure Active Directory (Azure AD). When you integrate WEDO with Azure AD, you can: |
| 25 | + |
| 26 | +* Control in Azure AD who has access to WEDO. |
| 27 | +* Enable your users to be automatically signed-in to WEDO 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/active-directory-appssoaccess-whatis). |
| 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 | +* WEDO single sign-on (SSO) enabled subscription. Please contact [WEDO Client support team ](mailto:[email protected]) to get a SSO subscription. |
| 38 | + |
| 39 | +## Scenario description |
| 40 | + |
| 41 | +In this tutorial, you configure and test Azure AD SSO in a test environment. |
| 42 | + |
| 43 | +* WEDO supports **SP and IDP** initiated SSO |
| 44 | + |
| 45 | +* [Once you configure the WEDO you can enforce session controls, which protect exfiltration and infiltration of your organization’s sensitive data in real-time. Session controls 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). |
| 46 | + |
| 47 | +## Adding WEDO from the gallery |
| 48 | + |
| 49 | +To configure the integration of WEDO into Azure AD, you need to add WEDO from the gallery to your list of managed SaaS apps. |
| 50 | + |
| 51 | +1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account. |
| 52 | +1. On the left navigation pane, select the **Azure Active Directory** service. |
| 53 | +1. Navigate to **Enterprise Applications** and then select **All Applications**. |
| 54 | +1. To add new application, select **New application**. |
| 55 | +1. In the **Add from the gallery** section, type **WEDO** in the search box. |
| 56 | +1. Select **WEDO** from results panel and then add the app. Wait a few seconds while the app is added to your tenant. |
| 57 | + |
| 58 | + |
| 59 | +## Configure and test Azure AD single sign-on for WEDO |
| 60 | + |
| 61 | +Configure and test Azure AD SSO with WEDO 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 WEDO. |
| 62 | + |
| 63 | +To configure and test Azure AD SSO with WEDO, complete the following building blocks: |
| 64 | + |
| 65 | +1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature. |
| 66 | + * **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon. |
| 67 | + * **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on. |
| 68 | +1. **[Configure WEDO SSO](#configure-wedo-sso)** - to configure the single sign-on settings on application side. |
| 69 | + * **[Create WEDO test user](#create-wedo-test-user)** - to have a counterpart of B.Simon in WEDO that is linked to the Azure AD representation of user. |
| 70 | +1. **[Test SSO](#test-sso)** - to verify whether the configuration works. |
| 71 | + |
| 72 | +## Configure Azure AD SSO |
| 73 | + |
| 74 | +Follow these steps to enable Azure AD SSO in the Azure portal. |
| 75 | + |
| 76 | +1. In the [Azure portal](https://portal.azure.com/), on the **WEDO** application integration page, find the **Manage** section and select **single sign-on**. |
| 77 | +1. On the **Select a single sign-on method** page, select **SAML**. |
| 78 | +1. On the **Set up single sign-on with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings. |
| 79 | + |
| 80 | +  |
| 81 | + |
| 82 | +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: |
| 83 | + |
| 84 | + a. In the **Identifier** text box, type a URL using the following pattern: |
| 85 | + `https://<SUBDOMAIN>.wedo.swiss/sp/acs` |
| 86 | + |
| 87 | + b. In the **Reply URL** text box, type a URL using the following pattern: |
| 88 | + `https://<SUBDOMAIN>.wedo.swiss/sp/acs` |
| 89 | + |
| 90 | +1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode: |
| 91 | + |
| 92 | + In the **Sign-on URL** text box, type a URL using the following pattern: |
| 93 | + `https://<SUBDOMAIN>.wedo.swiss/` |
| 94 | + |
| 95 | + > [!NOTE] |
| 96 | + > These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [WEDO 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. |
| 97 | + |
| 98 | +1. WEDO 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. |
| 99 | + |
| 100 | + | Name | Source Attribute| |
| 101 | + | ------------ | --------- | |
| 102 | + | email | user.email | |
| 103 | + | firstName | user.firstName | |
| 104 | + | lastName | user.lasttName | |
| 105 | + | userName | user.userName | |
| 106 | + |
| 107 | +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. |
| 108 | + |
| 109 | +  |
| 110 | + |
| 111 | +1. On the **Set up WEDO** section, copy the appropriate URL(s) based on your requirement. |
| 112 | + |
| 113 | +  |
| 114 | + |
| 115 | +### Create an Azure AD test user |
| 116 | + |
| 117 | +In this section, you'll create a test user in the Azure portal called B.Simon. |
| 118 | + |
| 119 | +1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**. |
| 120 | +1. Select **New user** at the top of the screen. |
| 121 | +1. In the **User** properties, follow these steps: |
| 122 | + 1. In the **Name** field, enter `B.Simon`. |
| 123 | + 1. In the **User name ** field, enter the [email protected]. For example, `[email protected]`. |
| 124 | + 1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box. |
| 125 | + 1. Click **Create**. |
| 126 | + |
| 127 | +### Assign the Azure AD test user |
| 128 | + |
| 129 | +In this section, you'll enable B.Simon to use Azure single sign-on by granting access to WEDO. |
| 130 | + |
| 131 | +1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**. |
| 132 | +1. In the applications list, select **WEDO**. |
| 133 | +1. In the app's overview page, find the **Manage** section and select **Users and groups**. |
| 134 | + |
| 135 | +  |
| 136 | + |
| 137 | +1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog. |
| 138 | + |
| 139 | +  |
| 140 | + |
| 141 | +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. |
| 142 | +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. |
| 143 | +1. In the **Add Assignment** dialog, click the **Assign** button. |
| 144 | + |
| 145 | +## Configure WEDO SSO |
| 146 | + |
| 147 | +Follow these steps to enable Azure AD SSO in WEDO. |
| 148 | + |
| 149 | +1. Log in [WEDO](https://login.wedo.swiss/). You need to have **administrator role**. |
| 150 | +1. In the Profile settings, select the menu **Authentication** in the section **Network settings**. |
| 151 | +1. On the **SAML Authentication** page, perform the following steps: |
| 152 | + |
| 153 | +  |
| 154 | + |
| 155 | + a. Enable **SAML Authentication**. |
| 156 | + |
| 157 | + b. Select the **Identity Provider metadata (XML)** tab. |
| 158 | + |
| 159 | + c. Open the downloaded **Federation Metadata XML** from Azure portal into Notepad and copy the content of metadata XML and paste it into **X.509 Certificate** textbox. |
| 160 | + |
| 161 | + d. Click on **Save** |
| 162 | + |
| 163 | +### Create WEDO test user |
| 164 | + |
| 165 | +In this section, you'll create a test user in WEDO called Bob Simon. Information must matches from *Create an Azure AD test user*. |
| 166 | + |
| 167 | +1. From the Profile setting in WEDO, select **Users** from *Network settings* section. |
| 168 | +1. Click **Add user**. |
| 169 | +1. In the Add user popup, fill the user's information |
| 170 | + |
| 171 | + a. First name `B`. |
| 172 | + |
| 173 | + b. Last name `Simon`. |
| 174 | + |
| 175 | + c. Enter the email `[email protected]`. For example, `[email protected]`. It is mandatory to have email with the same domain as your company short name. |
| 176 | + |
| 177 | + d. User type `User`. |
| 178 | + |
| 179 | + e. Click **Create user**. |
| 180 | + |
| 181 | + f. In the *Select teams* page, click **Save**. |
| 182 | + |
| 183 | + g. In the *Invite user* page, click **Yes**. |
| 184 | + |
| 185 | +1. Validate the user using the link you received by email |
| 186 | + |
| 187 | +> [!NOTE] |
| 188 | +> If you want to create a fake user (email above does not exist in your network), contact [our support](mailto:[email protected]) to validate the user*. |
| 189 | +
|
| 190 | +## Test SSO |
| 191 | + |
| 192 | +In this section, you test your Azure AD single sign-on configuration using the Access Panel. |
| 193 | + |
| 194 | +When you click the WEDO tile in the Access Panel, you should be automatically signed in to the WEDO 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). |
| 195 | + |
| 196 | +## Additional resources |
| 197 | + |
| 198 | +- [ 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) |
| 199 | + |
| 200 | +- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis) |
| 201 | + |
| 202 | +- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview) |
| 203 | + |
| 204 | +- [Try WEDO with Azure AD](https://aad.portal.azure.com/) |
| 205 | + |
| 206 | +- [What is session control in Microsoft Cloud App Security?](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad) |
| 207 | + |
| 208 | +- [How to protect WEDO with advanced visibility and controls](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad) |
0 commit comments