Edit

Tutorial: Azure AD SSO integration with NetMotion Mobility

  • Article
  • 5 minutes to read

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:

  • Control in Azure AD who has access to NetMotion Mobility.
  • Enable users to be signed-in with a NetMotion Mobility client with their Azure AD accounts.
  • Manage your accounts in one central location - the Azure portal.

Prerequisites

To get started, you need the following items:

  • An Azure AD subscription. If you don't have a subscription, you can get a free account.
  • NetMotion Mobility 12.50 or later.
  • Along with Cloud Application Administrator, Application Administrator can also add or manage applications in Azure AD. For more information, see Azure built-in roles.

Scenario description

In this tutorial, you configure and test Azure AD SSO in a test environment.

  • NetMotion Mobility supports SP initiated SSO.
  • NetMotion Mobility supports Just In Time user provisioning.

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.

  1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
  2. On the left navigation pane, select the Azure Active Directory service.
  3. Navigate to Enterprise Applications and then select All Applications.
  4. To add new application, select New application.
  5. In the Add from the gallery section, type NetMotion Mobility in the search box.
  6. Select NetMotion Mobility from results panel and then add the app. Wait a few seconds while the app is added to your tenant.

Alternatively, you can also use the Enterprise App Configuration Wizard. In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, as well as walk through the SSO configuration as well. Learn more about Microsoft 365 wizards.

Configure and test Azure AD SSO for NetMotion Mobility

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.

To configure and test Azure AD SSO with NetMotion Mobility, perform the following steps:

  1. Configure Mobility for SAML-based Authentication - to enable end users to authenticate using their Azure AD credentials.
  2. Configure Azure AD SSO - to enable your users to use this feature.
    1. Create an Azure AD test user - to test Azure AD single sign-on with B.Simon.
    2. Assign the Azure AD test user - to enable B.Simon to use Azure AD single sign-on.
  3. Configure NetMotion Mobility SSO - to configure the single sign-on settings on application side.
    1. 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.
  4. Test SAML-based User Authentication with the Mobility Client - to verify whether the configuration works.

Configure Mobility for SAML-based Authentication

On the Mobility console, follow the procedures in the Mobility Administrator Guide to accomplish the following:

  1. Create an authentication profile for SAML – to enable a set of Mobility users to use the SAML protocol.
  2. Configure SAML-based user authentication, in Mobility – to set an SP URL and generate the mobilitySPmetadata.xml file which you will later import into Azure AD.

Configure Azure AD SSO

Follow these steps to enable Azure AD SSO in the Azure portal.

  1. In the Azure portal, on the NetMotion Mobility application integration page, find the Manage section and select single sign-on.

  2. On the Select a single sign-on method page, select SAML.

  3. 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.

    Screenshot shows to choose metadata file.

  4. 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:

    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: https://<YourMobilityServerName>.<CustomerDomain>.<tld>/

    b. In the Reply URL text box, verify that the URL is using the following pattern: https://<YourMobilityServerName>.<CustomerDomain>.<tld>/saml/login

  5. 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.

    Screenshot shows the Certificate download link.

Create an Azure AD test user

In this section, you'll create a test user in the Azure portal called B.Simon.

  1. From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
  2. Select New user at the top of the screen.
  3. In the User properties, follow these steps:
    1. In the Name field, enter B.Simon.
    2. In the User name field, enter the username@companydomain.extension. For example, B.Simon@contoso.com.
    3. Select the Show password check box, and then write down the value that's displayed in the Password box.
    4. Click Create.

Assign the Azure AD test user

In this section, you'll enable B.Simon to use Azure single sign-on by granting access to NetMotion Mobility.

  1. In the Azure portal, select Enterprise Applications, and then select All applications.
  2. In the applications list, select NetMotion Mobility.
  3. In the app's overview page, find the Manage section and select Users and groups.
  4. Select Add user, then select Users and groups in the Add Assignment dialog.
  5. In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
  6. 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.
  7. In the Add Assignment dialog, click the Assign button.

Configure NetMotion Mobility SSO

Follow the instructions in the Mobility Administrator Guide for Configuring IdP Settings in the Mobility Console, import the Azure AD metadata file back into your Mobility server and complete the steps for IdP configuration.

  1. Once the Mobility authentication settings are configured, assign them to devices or device groups.
  2. Go to Mobility console > Configure > Client Settings and select the device or device group on the left that will use SAML-based authentication.
  3. Select Authentication - Settings Profile and choose the settings profile you created from the drop-down list.
  4. When you click Apply, the selected device or group is subscribed to the non-default settings.

Create NetMotion Mobility test user

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.

Test SAML-based User Authentication with the Mobility Client

In this section, you test your Azure AD SAML configuration for client authentication.

  1. Follow the guidance in Configuring Mobility Clients, 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.
  2. If you encounter problems during the test, follow the guidance under Troubleshooting the Mobility Client.