Skip to main content
McAfee Enterprise MVISION Cloud

Integrate Azure Active Directory with IAM enabled MVISION Cloud

To integrate Azure Active Directory (AD) with IAM enabled MVISION Cloud, you must add MVISION Cloud from the Azure Gallery, configure SAML SSO in MVISION Cloud, then reconfigure Azure AD SSO.

Prerequisites

Before you configure, make sure you have the following prerequisites:

  • An Azure AD account with Azure AD Premium Subscription. Activate the subscription from the Azure free account.
  • Access to MVISION Cloud tenant with the provisioned user.

Step 1: Add MVISION Cloud from the Gallery

To add MVISION Cloud  from the gallery, perform the following activities:

  1. Log in to the Azure portal
  2. On the left pane, click the Azure Active Directory icon.
    clipboard_e53b81f918840534ed641ed4800b86eb1.png
  3. Go to Enterprise applications and then select All applications.
    clipboard_e459150441370d2c7b65aa74a7ad7a2e5.png
  4. To add a new application, click New application.
    clipboard_e8b9396ecc5bde79156a72752f690acf4.png
  5. In the search box, enter Mvision and select MVISION Cloud Azure AD SSO Configuration from the result pane. To add the application, click Add.
    clipboard_e26473d320204d8d5f22c986a3d930c73.png
  6. Click the MVISION Cloud Azure AD SSO Configuration application. Click Set up single sign on.
    clipboard_e322c3b2e64197006639ad40d3cb90e6c.png
  7. Edit the Basic SAML Configuration and configure it with default values.
    clipboard_e127db15c9caedb2049867b8b209f6399.png

NOTE: The default generated values for the Azure AD SSO URL, Identifier, and Certificates are used in MVISION Cloud SAML Configuration.

  1. Download the Certificate (Base64) and save the Login URL, Azure AD Identifier to use it in MVISION Cloud.
    clipboard_ee686e91d453b89741c105087c21b241d.png
  2. Do not close the session, as you need to reconfigure this page after the MVISION Cloud configuration is completed.

Step 2: Configure SAML SSO in MVISION Cloud

  1. Login to MVISION Cloud .
  2. Go to Settings > User Management > SAML Configuration.
  3. Enter these details copied from Azure AD:
    • Azure AD Issuer. Enter the copied URL.
    • Login URL. Enter the App Federation Metadata Url copied from Azure AD.
    • Upload the Azure AD certificate.
      clipboard_e14cd682dd507c646e95a3f630f4858c1.png
  4. Click Save.
    Once the configuration is saved in MVISION Cloud, the Audience and Assertion Consumer Service URL is displayed under Service Provider.

Step 3: Reconfigure MVISION Cloud Azure AD SSO

  1. Go to the Azure AD Configuration and edit Basic SAML Configuration.
  2. Update Identifier and Reply URL (Assertion Consumer Service URL) and click Save.
    clipboard_e0a247f9361a71b5f167f0190ff4f5c4f.png

Assign the Application to Users 

  1. Click Users and groups.
  2. Click Add User.
    clipboard_e93702a50199790bf80c15e4efa25ce51.png
  3. Search the required users to provide access to MVISION Cloud and select the Users and assign the application.
    clipboard_efd9c1e76a5adf0bbdad7eb67a7ee0591.png

Step 4: Validate the Azure AD SSO

As of now, IAM enabled tenant only supports IDP initiated SSO only.

IDP Initiated Login

  1. Log In to https://myapps.microsoft.com/ with the user assigned MVISION Cloud application.
  2. Click MVISION Cloud application.
    You are successfully login to IAM enabled MVISION Cloud tenant.

Common Errors and Troubleshooting Steps

Azure SSO Errors

Misconfigured identity Provider. Check your configuration and try again. This error occurs when you have User Attributes & Claims using the Namespace URL format.
clipboard_e465689c951273af3a05dde94843126a7.png

Troubleshooting

In order to verify and resolve the above error, perform the following activities.

  1. Go to MVISION Cloud application created in Azure AD.
  2. Under User Attributes & Claims, edit and make sure that the below claims are configured accordingly:
    • firstName = user.givenname
    • lastName = usere.surname
    • email = user.userprincipalname
      clipboard_e73126048cee5fca8cf71395f3ea4339b.png
  3. Under Additional claims, if you see URLs for Claim name, then those URLs need to be removed.
    clipboard_ea4a5366b4b117084e0db96c1cbb6ad9e.png
  4. Edit the respective Claim name and remove the URL from the Namespace and leave it blank.
    clipboard_ede56bfe87bd90d25b813a9298b4e177b.png
  5. After removing the Claim name URLs, the attributes are displayed as shown below and this resolves your error.
    clipboard_e22e10e772e8f70e974c04a7e6c48de35.png
  • Was this article helpful?