|
| 1 | +--- |
| 2 | +title: Azure Active Directory SSO integration with Beable |
| 3 | +description: Learn how to configure single sign-on between Azure Active Directory and Beable. |
| 4 | +services: active-directory |
| 5 | +author: jeevansd |
| 6 | +manager: CelesteDG |
| 7 | +ms.reviewer: CelesteDG |
| 8 | +ms.service: active-directory |
| 9 | +ms.subservice: saas-app-tutorial |
| 10 | +ms.workload: identity |
| 11 | +ms.topic: how-to |
| 12 | +ms.date: 02/09/2023 |
| 13 | +ms.author: jeedes |
| 14 | + |
| 15 | +--- |
| 16 | + |
| 17 | +# Azure Active Directory SSO integration with Beable |
| 18 | + |
| 19 | +In this article, you learn how to integrate Beable with Azure Active Directory (Azure AD). Beable Education offers interactive & engaging online learning platforms, textbooks & mobile apps for students to access information & succeed in studies. When you integrate Beable with Azure AD, you can: |
| 20 | + |
| 21 | +* Control in Azure AD who has access to Beable. |
| 22 | +* Enable your users to be automatically signed-in to Beable with their Azure AD accounts. |
| 23 | +* Manage your accounts in one central location - the Azure portal. |
| 24 | + |
| 25 | +You'll configure and test Azure AD single sign-on for Beable in a test environment. Beable supports **IDP** initiated single sign-on. |
| 26 | + |
| 27 | +## Prerequisites |
| 28 | + |
| 29 | +To integrate Azure Active Directory with Beable, you need: |
| 30 | + |
| 31 | +* An Azure AD user account. If you don't already have one, you can [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F). |
| 32 | +* One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal. |
| 33 | +* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/). |
| 34 | +* Beable single sign-on (SSO) enabled subscription. |
| 35 | + |
| 36 | +## Add application and assign a test user |
| 37 | + |
| 38 | +Before you begin the process of configuring single sign-on, you need to add the Beable application from the Azure AD gallery. You need a test user account to assign to the application and test the single sign-on configuration. |
| 39 | + |
| 40 | +### Add Beable from the Azure AD gallery |
| 41 | + |
| 42 | +Add Beable from the Azure AD application gallery to configure single sign-on with Beable. For more information on how to add application from the gallery, see the [Quickstart: Add application from the gallery](../manage-apps/add-application-portal.md). |
| 43 | + |
| 44 | +### Create and assign Azure AD test user |
| 45 | + |
| 46 | +Follow the guidelines in the [create and assign a user account](../manage-apps/add-application-portal-assign-users.md) article to create a test user account in the Azure portal called B.Simon. |
| 47 | + |
| 48 | +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, and assign roles. The wizard also provides a link to the single sign-on configuration pane in the Azure portal. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides). |
| 49 | + |
| 50 | +## Configure Azure AD SSO |
| 51 | + |
| 52 | +Complete the following steps to enable Azure AD single sign-on in the Azure portal. |
| 53 | + |
| 54 | +1. In the Azure portal, on the **Beable** application integration page, find the **Manage** section and select **single sign-on**. |
| 55 | +1. On the **Select a single sign-on method** page, select **SAML**. |
| 56 | +1. On the **Set up single sign-on with SAML** page, select the pencil icon for **Basic SAML Configuration** to edit the settings. |
| 57 | + |
| 58 | +  |
| 59 | + |
| 60 | +1. On the **Basic SAML Configuration** section, perform the following steps: |
| 61 | + |
| 62 | + a. In the **Identifier** textbox, type a URL using the following pattern: |
| 63 | + `https://<SUBDOMAIN>.beable.com` |
| 64 | + |
| 65 | + b. In the **Reply URL** textbox, type a URL using the following pattern: |
| 66 | + `https://prod-literacy-backend-alb-12049610218161332941.beable.com/login/ssoVerification/?providerId=1466658d-11ae-11ed-b1a0-b9e58c7ef6cc&identifier=<DOMAIN>` |
| 67 | + |
| 68 | + > [!Note] |
| 69 | + > These values are not real. Update these values with the actual Identifier and Reply URL. Contact [Beable support team](https://beable.com/contact/) to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal. |
| 70 | + |
| 71 | +1. Beable 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. |
| 72 | + |
| 73 | +  |
| 74 | + |
| 75 | +1. In addition to above, Beable 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. |
| 76 | + |
| 77 | + | Name | Source Attribute| |
| 78 | + | ---------------| --------- | |
| 79 | + | usertype | user.usertype | |
| 80 | + | preferredlanguage | user.preferredlanguage | |
| 81 | + | assignedroles | user.assignedroles | |
| 82 | + |
| 83 | +1. On the **Set-up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Certificate (Base64)** and select **Download** to download the certificate and save it on your computer. |
| 84 | + |
| 85 | +  |
| 86 | + |
| 87 | +1. On the **Set up Beable** section, copy the appropriate URL(s) based on your requirement. |
| 88 | + |
| 89 | +  |
| 90 | + |
| 91 | +## Configure Beable SSO |
| 92 | + |
| 93 | +To configure single sign-on on **Beable** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [Beable support team](https://beable.com/contact/). They set this setting to have the SAML SSO connection set properly on both sides |
| 94 | + |
| 95 | +### Create Beable test user |
| 96 | + |
| 97 | +In this section, the users are rostered in Beable. Work with [Beable support team](https://beable.com/contact/) to provision the users in the Beable platform. |
| 98 | + |
| 99 | +## Test SSO |
| 100 | + |
| 101 | +In this section, you test your Azure AD single sign-on configuration with following options. |
| 102 | + |
| 103 | +* Click on Test this application in Azure portal and you should be automatically signed in to the Beable for which you set up the SSO. |
| 104 | + |
| 105 | +* You can use Microsoft My Apps. When you click the Beable tile in the My Apps, you should be automatically signed in to the Beable 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). |
| 106 | + |
| 107 | +## Next steps |
| 108 | + |
| 109 | +Once you configure Beable 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). |
0 commit comments