Merge pull request #178125 from bhavana-129/v-client

Product Backlog Item 1642411: SaaS App Tutorial: V-Client

Author: ttorble

articles/active-directory/saas-apps/toc.yml

@@ -2156,6 +2156,8 @@
         href: uservoice-tutorial.md
       - name: ValidSign
         href: validsign-tutorial.md
+      - name: V-Client
+        href: v-client-tutorial.md  
       - name: VECOS Releezme Locker management system
         href: vecos-releezme-locker-management-system-tutorial.md  
       - name: Velpic SAML

articles/active-directory/saas-apps/v-client-tutorial.md

@@ -0,0 +1,148 @@
+---
+title: 'Tutorial: Azure AD SSO integration with V-Client'
+description: Learn how to configure single sign-on between Azure Active Directory and V-Client.
+services: active-directory
+author: jeevansd
+manager: CelesteDG
+ms.reviewer: CelesteDG
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.topic: tutorial
+ms.date: 11/01/2021
+ms.author: jeedes
+
+---
+
+# Tutorial: Azure AD SSO integration with V-Client
+
+In this tutorial, you'll learn how to integrate V-Client with Azure Active Directory (Azure AD). When you integrate V-Client with Azure AD, you can:
+
+* Control in Azure AD who has access to V-Client.
+* Enable your users to be automatically signed-in to V-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](https://azure.microsoft.com/free/).
+* V-Client single sign-on (SSO) enabled subscription.
+
+## Scenario description
+
+In this tutorial, you configure and test Azure AD SSO in a test environment.
+
+* V-Client supports **IDP** initiated SSO.
+
+## Add V-Client from the gallery
+
+To configure the integration of V-Client into Azure AD, you need to add V-Client 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.
+1. On the left navigation pane, select the **Azure Active Directory** service.
+1. Navigate to **Enterprise Applications** and then select **All Applications**.
+1. To add new application, select **New application**.
+1. In the **Add from the gallery** section, type **V-Client** in the search box.
+1. Select **V-Client** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
+
+## Configure and test Azure AD SSO for V-Client
+
+Configure and test Azure AD SSO with V-Client 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 V-Client.
+
+To configure and test Azure AD SSO with V-Client, perform the following steps:
+
+1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
+    1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
+    1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
+1. **[Configure V-Client SSO](#configure-v-client-sso)** - to configure the single sign-on settings on application side.
+    1. **[Create V-Client test user](#create-v-client-test-user)** - to have a counterpart of B.Simon in V-Client that is linked to the Azure AD representation of user.
+1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
+
+## Configure Azure AD SSO
+
+Follow these steps to enable Azure AD SSO in the Azure portal.
+
+1. In the Azure portal, on the **V-Client** application integration page, find the **Manage** section and select **single sign-on**.
+1. On the **Select a single sign-on method** page, select **SAML**.
+1. On the **Set up single sign-on with SAML** page, click the pencil icon for **Basic SAML Configuration** to edit the settings.
+
+   ![Edit Basic SAML Configuration](common/edit-urls.png)
+
+1. On the **Basic SAML Configuration** section, perform the following steps:
+
+    a. In the **Identifier** text box, type a URL using one of the following patterns:
+
+    | **Identifier** |
+    |--------|
+    | `https://<Environment>.verona.amigram.xyz/<CustomerName>` |
+    | ` https://<Environment>.all-cloud.jp/<CustomerName>` |
+
+    b. In the **Reply URL** text box, type a URL using one of the following patterns:
+
+    | **Reply URL** |
+    |------|
+    | `https://<Environment>-api.verona.amigram.xyz/id/saml2/acs` |
+    | `https://<Environment>-api.all-cloud.jp/id/saml2/acs` |
+
+	> [!NOTE]
+	> These values are not real. Update these values with the actual Identifier and Reply URL. Contact [V-Client 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.
+
+1. V-Client 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.
+
+	![image](common/default-attributes.png)
+
+1. In addition to above, V-Client 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|
+	| ------------- | --------- |
+	| oid | user.objectid |
+    | displayname | user.displayname |
+
+1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section,  find **Certificate (PEM)** and select **Download** to download the certificate and save it on your computer.
+
+	![The Certificate download link](common/certificate-base64-download.png)
+
+### 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**.
+1. Select **New user** at the top of the screen.
+1. In the **User** properties, follow these steps:
+   1. In the **Name** field, enter `B.Simon`.  
+   1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
+   1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
+   1. 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 V-Client.
+
+1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
+1. In the applications list, select **V-Client**.
+1. In the app's overview page, find the **Manage** section and select **Users and groups**.
+1. Select **Add user**, 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.
+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.
+1. In the **Add Assignment** dialog, click the **Assign** button.
+
+## Configure V-Client SSO
+
+To configure single sign-on on **V-Client** side, you need to send the downloaded **Certificate (PEM)** and appropriate copied URLs from Azure portal to [V-Client support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
+
+### Create V-Client test user
+
+In this section, you create a user called Britta Simon in V-Client. Work with [V-Client support team](mailto:[email protected]) to add the users in the V-Client platform. Users must be created and activated before you use single sign-on.
+
+## Test SSO
+
+In this section, you test your Azure AD single sign-on configuration with following options.
+
+* Click on Test this application in Azure portal and you should be automatically signed in to the V-Client for which you set up the SSO.
+
+* You can use Microsoft My Apps. When you click the V-Client tile in the My Apps, you should be automatically signed in to the V-Client for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
+
+## Next steps
+
+Once you configure V-Client 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 Cloud App Security](/cloud-app-security/proxy-deployment-aad).