Merge pull request #247092 from Harshita-130901/granite

Product Backlog Item 2653977: SaaS App Tutorial: Granite

Author: ttorble

articles/active-directory/saas-apps/granite-tutorial.md

@@ -0,0 +1,153 @@
+---
+title: Microsoft Entra SSO integration with Granite
+description: Learn how to configure single sign-on between Microsoft Entra ID and Granite.
+services: active-directory
+author: jeevansd
+manager: CelesteDG
+ms.reviewer: CelesteDG
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.topic: how-to
+ms.date: 09/25/2023
+ms.author: jeedes
+
+---
+
+# Microsoft Entra SSO integration with Granite
+
+In this tutorial, you learn how to integrate Granite with Microsoft Entra ID. When you integrate Granite with Microsoft Entra ID, you can:
+
+* Control in Microsoft Entra ID who has access to Granite.
+* Enable your users to be automatically signed-in to Granite with their Microsoft Entra accounts.
+* Manage your accounts in one central location.
+
+## Prerequisites
+
+To integrate Microsoft Entra ID with Granite, you need:
+
+* A Microsoft Entra subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
+* Granite single sign-on (SSO) enabled subscription.
+
+## Scenario description
+
+In this tutorial, you configure and test Microsoft Entra SSO in a test environment.
+
+* Granite supports **SP** initiated SSO.
+* Granite supports **Just In Time** user provisioning.
+
+## Adding Granite from the gallery
+
+To configure the integration of Granite into Microsoft Entra ID, you need to add Granite from the gallery to your list of managed SaaS apps.
+
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
+1. Browse to **Identity** > **Applications** > **Enterprise applications** > **New application**.
+1. In the **Add from the gallery** section, type **Granite** in the search box.
+1. Select **Granite** 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](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, and walk through the SSO configuration as well. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides)
+
+## Configure and test Microsoft Entra SSO for Granite
+
+Configure and test Microsoft Entra SSO with Granite 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 Granite.
+
+To configure and test Microsoft Entra SSO with Granite, perform the following steps:
+
+1. **[Configure Microsoft Entra SSO](#configure-microsoft-entra-sso)** - to enable your users to use this feature.
+    1. **[Create a Microsoft Entra ID test user](#create-a-microsoft-entra-id-test-user)** - to test Microsoft Entra single sign-on with B.Simon.
+    1. **[Assign the Microsoft Entra ID test user](#assign-the-microsoft-entra-id-test-user)** - to enable B.Simon to use Microsoft Entra single sign-on.
+1. **[Configure Granite SSO](#configure-granite-sso)** - to configure the single sign-on settings on application side.
+    1. **[Create Granite test user](#create-granite-test-user)** - to have a counterpart of B.Simon in Granite that is linked to the Microsoft Entra ID representation of user.
+1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
+
+## Configure Microsoft Entra SSO
+
+Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin center.
+
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
+1. Browse to **Identity** > **Applications** > **Enterprise applications** > **Granite** > **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.
+
+   ![Screenshot shows how to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration")
+
+1. On the **Basic SAML Configuration** section, perform the following steps:
+
+   a. In the **Identifier** textbox, type a value using the following pattern:
+   `<Customer_Name>.granitegrc.com`
+
+   b. In the **Reply URL** textbox, type a URL using the following pattern:
+   `https://<Customer_Name>.granitegrc.com/simplesaml/module.php/saml/sp/saml2-acs.php/default`
+
+   c. In the **Sign on URL** textbox, type a URL using the following pattern:
+	`https://<Customer_Name>.granitegrc.com`
+
+	> [!NOTE]
+   > These values are not real. Update these values with the actual Identifier, Reply URL and Sign on URL. Contact [Granite 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 Microsoft Entra admin center.
+
+1. Granite 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.
+
+	![Screenshot shows the image of attributes configuration.](common/default-attributes.png "Image")
+
+1. In addition to above, Granite 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|
+	| ---------------|  --------- |
+	| mail | user.mail |
+	| username | user.userprincipalname |
+	| groups | user.groups |
+   | company | user.companyname |
+   | department | user.department |
+   | objectid | user.objectid |
+
+1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer.
+
+	![Screenshot shows the Certificate download link.](common/copy-metadataurl.png "Certificate")
+
+### Create a Microsoft Entra ID test user
+
+In this section, you create a test user in the Microsoft Entra admin center called B.Simon.
+
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
+1. Browse to **Identity** > **Users** > **All users**.
+1. Select **New user** > **Create new user**, at the top of the screen.
+1. In the **User** properties, follow these steps:
+   1. In the **Display name** field, enter `B.Simon`.  
+   1. In the **User principal 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. Select **Review + create**.
+1. Select **Create**.
+
+### Assign the Microsoft Entra ID test user
+
+In this section, you enable B.Simon to use Microsoft Entra single sign-on by granting access to Granite.
+
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
+1. Browse to **Identity** > **Applications** > **Enterprise applications** > **Granite**.
+1. In the app's overview page, select **Users and groups**.
+1. 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.
+   1. If you're 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 Granite SSO
+
+To configure single sign-on on **Granite** side, you need to send the **App Federation Metadata Url** to [Granite support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
+
+### Create Granite test user
+
+In this section, a user called B.Simon is created in Granite. Granite supports just-in-time provisioning, which is enabled by default. There's no action item for you in this section. If a user doesn't already exist in Granite, a new one is created when you attempt to access Granite.
+
+## Test SSO 
+
+In this section, you test your Microsoft Entra single sign-on configuration with following options.
+ 
+* Click on **Test this application** in Microsoft Entra admin center. This will redirect to Granite Sign on URL where you can initiate the login flow.
+ 
+* Go to Granite Sign-on URL directly and initiate the login flow from there.
+ 
+* You can use Microsoft My Apps. When you click the Granite tile in the My Apps, this will redirect to Granite Sign on URL. 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 Granite 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](/cloud-app-security/proxy-deployment-any-app).

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

@@ -1111,6 +1111,8 @@
         href: grape-tutorial.md
       - name: Grammarly
         href: grammarly-tutorial.md  
+      - name: Granite
+        href: granite-tutorial.md
       - name: Greenhouse
         href: greenhouse-tutorial.md
       - name: Greenlight Compliant Access Management