|
| 1 | +--- |
| 2 | +title: 'Tutorial: Azure AD SSO integration with NetMotion Mobility' |
| 3 | +description: Learn how to configure single sign-on between Azure Active Directory and NetMotion Mobility. |
| 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: tutorial |
| 12 | +ms.date: 08/19/2022 |
| 13 | +ms.author: jeedes |
| 14 | + |
| 15 | +--- |
| 16 | + |
| 17 | +# Tutorial: Azure AD SSO integration with NetMotion Mobility |
| 18 | + |
| 19 | +In this tutorial, you'll learn how to integrate NetMotion Mobility with Azure Active Directory (Azure AD). When you integrate NetMotion Mobility with Azure AD, you can: |
| 20 | + |
| 21 | +* Control in Azure AD who has access to NetMotion Mobility. |
| 22 | +* Enable users to be signed-in with a NetMotion Mobility client with their Azure AD accounts. |
| 23 | +* Manage your accounts in one central location - the Azure portal. |
| 24 | + |
| 25 | +## Prerequisites |
| 26 | + |
| 27 | +To get started, you need the following items: |
| 28 | + |
| 29 | +* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/). |
| 30 | +* NetMotion Mobility 12.50 or later. |
| 31 | +* Along with Cloud Application Administrator, Application Administrator can also add or manage applications in Azure AD. |
| 32 | +For more information, see [Azure built-in roles](../roles/permissions-reference.md). |
| 33 | + |
| 34 | +## Scenario description |
| 35 | + |
| 36 | +In this tutorial, you configure and test Azure AD SSO in a test environment. |
| 37 | + |
| 38 | +* NetMotion Mobility supports **SP** initiated SSO. |
| 39 | +* NetMotion Mobility supports **Just In Time** user provisioning. |
| 40 | + |
| 41 | +## Add NetMotion Mobility from the gallery |
| 42 | + |
| 43 | +To configure the integration of NetMotion Mobility into Azure AD, you need to add NetMotion Mobility from the gallery to your list of managed SaaS apps. |
| 44 | + |
| 45 | +1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account. |
| 46 | +1. On the left navigation pane, select the **Azure Active Directory** service. |
| 47 | +1. Navigate to **Enterprise Applications** and then select **All Applications**. |
| 48 | +1. To add new application, select **New application**. |
| 49 | +1. In the **Add from the gallery** section, type **NetMotion Mobility** in the search box. |
| 50 | +1. Select **NetMotion Mobility** from results panel and then add the app. Wait a few seconds while the app is added to your tenant. |
| 51 | + |
| 52 | +## Configure and test Azure AD SSO for NetMotion Mobility |
| 53 | + |
| 54 | +Configure and test Azure AD SSO with NetMotion Mobility 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 NetMotion Mobility. |
| 55 | + |
| 56 | +To configure and test Azure AD SSO with NetMotion Mobility, perform the following steps: |
| 57 | + |
| 58 | +1. **[Configure Mobility for SAML-based Authentication](#configure-mobility-for-saml-based-authentication)** - to enable end users to authenticate using their Azure AD credentials. |
| 59 | +2. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature. |
| 60 | + 1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon. |
| 61 | + 1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on. |
| 62 | +3. **[Configure NetMotion Mobility SSO](#configure-netmotion-mobility-sso)** - to configure the single sign-on settings on application side. |
| 63 | + 1. **[Create NetMotion Mobility test user](#create-netmotion-mobility-test-user)** - to have a counterpart of B.Simon in NetMotion Mobility that is linked to the Azure AD representation of user. |
| 64 | +4. **[Test SAML-based User Authentication with the Mobility Client](#test-saml-based-user-authentication-with-the-mobility-client)** - to verify whether the configuration works. |
| 65 | + |
| 66 | +## Configure Mobility for SAML-based Authentication |
| 67 | + |
| 68 | +On the Mobility console, follow the procedures in the [Mobility Administrator Guide](https://help.netmotionsoftware.com/support/docs/MobilityXG/1250/help/mobilityhelp.htm#page/Mobility%2520Server%2Fintro.01.01.html%23) to accomplish the following: |
| 69 | +1. Create an [authentication profile](https://help.netmotionsoftware.com/support/docs/MobilityXG/1250/help/mobilityhelp.htm#page/Mobility%2520Server%2Fconfig.05.41.html%23ww2298330) for SAML – to enable a set of Mobility users to use the SAML protocol. |
| 70 | +2. Configure [SAML-based user authentication](https://help.netmotionsoftware.com/support/docs/MobilityXG/1250/help/mobilityhelp.htm#context/nmcfgapp/saml_userconfig), in Mobility – to set an SP URL and generate the mobilitySPmetadata.xml file which you will later import into Azure AD. |
| 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, on the **NetMotion Mobility** 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 on **Upload Metadata file** just above the **Basic SAML Configuration** section to import your mobilitySPMetadata.xml file into Azure AD. |
| 79 | + |
| 80 | +  |
| 81 | + |
| 82 | +1. After importing the metadata file, on the **Basic SAML Configuration** section, perform the following steps to verify that the XML import has been completed successfully: |
| 83 | + |
| 84 | + a. In the **Identifier** text box, verify that the URL is using the following pattern, where the variables in the following example URL match those for your Mobility server: |
| 85 | + `https://<YourMobilityServerName>.<CustomerDomain>.<tld>/` |
| 86 | + |
| 87 | + b. In the **Reply URL** text box, verify that the URL is using the following pattern: |
| 88 | + `https://<YourMobilityServerName>.<CustomerDomain>.<tld>/saml/login` |
| 89 | + |
| 90 | +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. |
| 91 | + |
| 92 | +  |
| 93 | + |
| 94 | +### Create an Azure AD test user |
| 95 | + |
| 96 | +In this section, you'll create a test user in the Azure portal called B.Simon. |
| 97 | + |
| 98 | +1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**. |
| 99 | +1. Select **New user** at the top of the screen. |
| 100 | +1. In the **User** properties, follow these steps: |
| 101 | + 1. In the **Name** field, enter `B.Simon`. |
| 102 | + 1. In the **User name ** field, enter the [email protected]. For example, `[email protected]`. |
| 103 | + 1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box. |
| 104 | + 1. Click **Create**. |
| 105 | + |
| 106 | +### Assign the Azure AD test user |
| 107 | + |
| 108 | +In this section, you'll enable B.Simon to use Azure single sign-on by granting access to NetMotion Mobility. |
| 109 | + |
| 110 | +1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**. |
| 111 | +1. In the applications list, select **NetMotion Mobility**. |
| 112 | +1. In the app's overview page, find the **Manage** section and select **Users and groups**. |
| 113 | +1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog. |
| 114 | +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. |
| 115 | +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. |
| 116 | +1. In the **Add Assignment** dialog, click the **Assign** button. |
| 117 | + |
| 118 | +## Configure NetMotion Mobility SSO |
| 119 | + |
| 120 | +Follow the instructions in the Mobility Administrator Guide for [Configuring IdP Settings in the Mobility Console](https://help.netmotionsoftware.com/support/docs/MobilityXG/1250/help/mobilityhelp.htm#context/nmcfgapp/saml_userconfig), import the Azure AD metadata file back into your Mobility server and complete the steps for IdP configuration. |
| 121 | + |
| 122 | +1. Once the Mobility authentication settings are configured, assign them to devices or device groups. |
| 123 | +1. Go to **Mobility console** > **Configure** > **Client Settings** and select the device or device group on the left that will use SAML-based authentication. |
| 124 | +1. Select **Authentication - Settings** Profile and choose the settings profile you created from the drop-down list. |
| 125 | +1. When you click **Apply**, the selected device or group is subscribed to the non-default settings. |
| 126 | + |
| 127 | +### Create NetMotion Mobility test user |
| 128 | + |
| 129 | +In this section, a user called B.Simon is created in NetMotion Mobility. NetMotion Mobility 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 NetMotion Mobility, a new one is created after authentication. |
| 130 | + |
| 131 | +## Test SAML-based User Authentication with the Mobility Client |
| 132 | + |
| 133 | +In this section, you test your Azure AD SAML configuration for client authentication. |
| 134 | + |
| 135 | +1. Follow the guidance in [Configuring Mobility Clients](https://help.netmotionsoftware.com/support/docs/MobilityXG/1250/help/mobilityhelp.htm#page/Mobility%2520Server%2Fusing.06.01.html%23), configure a client device that is assigned a SAML-based authentication profile to access the Mobility server pool you have configured for SAML-based authentication and attempt to connect. |
| 136 | +1. If you encounter problems during the test, follow the guidance under [Troubleshooting the Mobility Client](https://help.netmotionsoftware.com/support/docs/MobilityXG/1250/help/mobilityhelp.htm#page/Mobility%2520Server%2Ftrouble.14.02.html). |
0 commit comments