Tutorial: Microsoft Entra SSO integration with VIDA

Artikkel
03/25/2024

In this tutorial, you'll learn how to integrate VIDA with Microsoft Entra ID. When you integrate VIDA with Microsoft Entra ID, you can:

Control in Microsoft Entra ID who has access to VIDA.
Enable your users to be automatically signed-in to VIDA with their Microsoft Entra accounts.
Manage your accounts in one central location.

Prerequisites

To get started, you need the following items:

A Microsoft Entra subscription. If you don't have a subscription, you can get a free account.
VIDA single sign-on (SSO) enabled subscription.

Scenario description

In this tutorial, you configure and test Microsoft Entra SSO in a test environment.

VIDA supports SP initiated SSO.
VIDA supports Just In Time user provisioning.

Adding VIDA from the gallery

To configure the integration of VIDA into Microsoft Entra ID, you need to add VIDA from the gallery to your list of managed SaaS apps.

Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
Browse to Identity > Applications > Enterprise applications > New application.
In the Add from the gallery section, type VIDA in the search box.
Select VIDA 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 Microsoft Entra SSO for VIDA

Configure and test Microsoft Entra SSO with VIDA using a test user called B.Simon. For SSO to work, you need to establish a link relationship between a Microsoft Entra user and the related user in VIDA.

To configure and test Microsoft Entra SSO with VIDA, perform the following steps:

Configure Microsoft Entra SSO - to enable your users to use this feature.
1. Create a Microsoft Entra test user - to test Microsoft Entra single sign-on with B.Simon.
2. Assign the Microsoft Entra test user - to enable B.Simon to use Microsoft Entra single sign-on.
Configure VIDA SSO - to configure the single sign-on settings on application side.
1. Create VIDA test user - to have a counterpart of B.Simon in VIDA that is linked to the Microsoft Entra representation of user.
Test SSO - to verify whether the configuration works.

Configure Microsoft Entra SSO

Follow these steps to enable Microsoft Entra SSO.

Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
Browse to Identity > Applications > Enterprise applications > VIDA > Single sign-on.
On the Select a single sign-on method page, select SAML.
On the Set up single sign-on with SAML page, click the pencil icon for Basic SAML Configuration to edit the settings.
On the Basic SAML Configuration section, enter the values for the following fields:

a. In the Identifier (Entity ID) text box, type the value: urn:amazon:cognito:sp:eu-west-2_IDmTxjGr6

b. In the Reply URL text box, type the URL: https://vitruevida.auth.eu-west-2.amazoncognito.com/saml2/idpresponse

c. In the Sign-on URL text box, type a URL using the following pattern:

https://vitruevida.com/?teamid=<ID>&idp=<IDP_NAME>

Note

The Sign-on URL value is not real. Update the value with the actual Sign-On URL. Contact VIDA Client support team to get the value. You can also refer to the patterns shown in the Basic SAML Configuration section.
VIDA 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.
In addition to above, VIDA application expects few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements.

Name Source Attribute

assignedroles user.assignedroles
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.
On the Set up VIDA section, copy the appropriate URL(s) based on your requirement.

Name	Source Attribute
assignedroles	user.assignedroles

Create a Microsoft Entra test user

In this section, you'll create a test user called B.Simon.

Sign in to the Microsoft Entra admin center as at least a User Administrator.
Browse to Identity > Users > All users.
Select New user > Create new user, at the top of the screen.
In the User properties, follow these steps:
1. In the Display name field, enter B.Simon.
2. In the User principal 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. Select Review + create.
Select Create.

Assign the Microsoft Entra test user

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

Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
Browse to Identity > Applications > Enterprise applications > VIDA.
In the app's overview page, select Users and groups.
Select Add user/group, then select Users and groups in the Add Assignment dialog.
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.
2. 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.
3. In the Add Assignment dialog, click the Assign button.

Configure Role-Based Single Sign-On in VIDA

To associate a VIDA role with the Microsoft Entra user, you must create a role in Microsoft Entra ID by following these steps:

a. Sign on to the Microsoft Graph Explorer.

b. Click modify permissions to obtain required permissions for creating a role.

c. Select the following permissions from the list and click Modify Permissions, as shown in the following figure.

Note

After permissions are granted, log on to the Graph Explorer again.

d. On the Graph Explorer page, select GET from the first drop-down list and beta from the second drop-down list. Then enter https://graph.microsoft.com/beta/servicePrincipals in the field next to the drop-down lists, and click Run Query.

Note

If you are using multiple directories, you can enter https://graph.microsoft.com/beta/contoso.com/servicePrincipals in the field of the query.

e. In the Response Preview section, extract the appRoles property from the 'Service Principal' for subsequent use.

Note

You can locate the appRoles property by entering https://graph.microsoft.com/beta/servicePrincipals/<objectID> in the field of the query. Note that the objectID is the object ID you have copied from the Microsoft Entra ID Properties page.

f. Go back to the Graph Explorer, change the method from GET to PATCH, paste the following content into the Request Body section, and click Run Query:
```
{ 
"appRoles": [
    {
        "allowedMemberTypes": [
        "User"
        ],
        "description": "User",
        "displayName": "User",
        "id": "18d14569-c3bd-439b-9a66-3a2aee01****",
        "isEnabled": true,
        "origin": "Application",
        "value": null
    },
    {
        "allowedMemberTypes": [
        "User"
        ],
        "description": "msiam_access",
        "displayName": "msiam_access",
        "id": "b9632174-c057-4f7e-951b-be3adc52****",
        "isEnabled": true,
        "origin": "Application",
        "value": null
    },
    {
    "allowedMemberTypes": [
        "User"
    ],
    "description": "VIDACompanyAdmin",
    "displayName": "VIDACompanyAdmin",
    "id": "293414bb-2215-48b4-9864-64520937d437",
    "isEnabled": true,
    "origin": "ServicePrincipal",
    "value": "VIDACompanyAdmin"
    },
    {
    "allowedMemberTypes": [
        "User"
    ],
    "description": "VIDATeamAdmin",
    "displayName": "VIDATeamAdmin",
    "id": "2884f1ae-5c0d-4afd-bf28-d7d11a3d7b2c",
    "isEnabled": true,
    "origin": "ServicePrincipal",
    "value": "VIDATeamAdmin"
    },
    {
    "allowedMemberTypes": [
        "User"
    ],
    "description": "VIDAUser",
    "displayName": "VIDAUser",
    "id": "37b3218c-0c06-484f-90e6-4390ce5a8787",
    "isEnabled": true,
    "origin": "ServicePrincipal",
    "value": "VIDAUser"
    }
]
}
```
Note

Microsoft Entra ID will send the value of these roles as the claim value in SAML response. However, you can only add new roles after the msiam_access part for the patch operation. To smooth the creation process, we recommend that you use an ID generator, such as GUID Generator, to generate IDs in real time.

g. After the 'Service Principal' is patched with the required role, attach the role with the Microsoft Entra user (B.Simon) by following the steps of Assign the Microsoft Entra test user section of the tutorial.

Configure VIDA SSO

To configure single sign-on on VIDA side, you need to send the downloaded Federation Metadata XML and appropriate copied URLs from the application configuration to VIDA support team. They set this setting to have the SAML SSO connection set properly on both sides.

Create VIDA test user

In this section, a user called Britta Simon is created in VIDA. VIDA 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 VIDA, a new one is created after authentication.

Test SSO

In this section, you test your Microsoft Entra single sign-on configuration with following options.

Click on Test this application, this will redirect to VIDA Sign-on URL where you can initiate the login flow.
Go to VIDA Sign-on URL directly and initiate the login flow from there.
You can use Microsoft My Apps. When you click the VIDA tile in the My Apps, this will redirect to VIDA Sign-on URL. For more information, see Microsoft Entra My Apps.

Next steps

Once you configure VIDA you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. Learn how to enforce session control with Microsoft Defender for Cloud Apps.

Del via