Skip to content

Commit 30d794f

Browse files
authored
Merge pull request #229237 from bhavana-129/ledgy
Product Backlog Item 2446619: SaaS App Tutorial: Ledgy
2 parents 81cacd1 + 6c038ae commit 30d794f

File tree

2 files changed

+126
-0
lines changed

2 files changed

+126
-0
lines changed
Lines changed: 124 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,124 @@
1+
---
2+
title: Azure Active Directory SSO integration with Ledgy
3+
description: Learn how to configure single sign-on between Azure Active Directory and Ledgy.
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: 03/02/2023
13+
ms.author: jeedes
14+
15+
---
16+
17+
# Azure Active Directory SSO integration with Ledgy
18+
19+
In this article, you learn how to integrate Ledgy with Azure Active Directory (Azure AD). Automate your equity. Grant shares and options to employees around the world, integrate equity into all your key systems, and help your team understand their ownership stakes. When you integrate Ledgy with Azure AD, you can:
20+
21+
* Control in Azure AD who has access to Ledgy.
22+
* Enable your users to be automatically signed-in to Ledgy with their Azure AD accounts.
23+
* Manage your accounts in one central location - the Azure portal.
24+
25+
You configure and test Azure AD single sign-on for Ledgy in a test environment. Ledgy supports both **SP** and **IDP** initiated single sign-on and **Just In Time** user provisioning.
26+
27+
## Prerequisites
28+
29+
To integrate Azure Active Directory with Ledgy, 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+
* Ledgy 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 Ledgy 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 Ledgy from the Azure AD gallery
41+
42+
Add Ledgy from the Azure AD application gallery to configure single sign-on with Ledgy. 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 **Ledgy** 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+
![Screenshot shows how to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration")
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://app.ledgy.com/auth/saml/<orgSlug>/metadata.xml`
64+
65+
b. In the Reply URL textbox, type a URL using the following pattern:
66+
`https://app.ledgy.com/auth/saml/<orgSlug>/acs`
67+
68+
1. If you wish to configure the application in SP initiated mode, then perform the following step:
69+
70+
In the **Sign on URL** textbox, type the URL:
71+
`https://app.ledgy.com/login`
72+
73+
> [!NOTE]
74+
> These values are not real. Update these values with the actual Identifier and Reply URL. Contact [Ledgy 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.
75+
76+
1. Ledgy 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.
77+
78+
![Screenshot shows the image of attributes configuration.](common/default-attributes.png "Image")
79+
80+
1. In addition to above, Ledgy application expects few more attributes to be passed back in SAML response, which are shown. These attributes are also pre populated but you can review them as per your requirements.
81+
82+
| Name | Source Attribute|
83+
| ---------------| --------- |
84+
| email | user.mail |
85+
| ID | user.userprincipalname |
86+
| firstName | user.givenname |
87+
| lastName | user.surname |
88+
89+
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.
90+
91+
![Screenshot shows the Certificate download link.](common/copy-metadataurl.png "Certificate")
92+
93+
## Configure Ledgy SSO
94+
95+
To configure single sign-on on **Ledgy** side, you need to send the **App Federation Metadata Url** to [Ledgy support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
96+
97+
### Create Ledgy test user
98+
99+
In this section, a user called B.Simon is created in Ledgy. Ledgy supports just-in-time user provisioning, which is enabled by default. There's no action item for you in this section. If a user doesn't already exist in Ledgy, a new one is commonly created after authentication.
100+
101+
## Test SSO
102+
103+
In this section, you test your Azure AD single sign-on configuration with following options.
104+
105+
#### SP initiated
106+
107+
* Click on **Test this application** in Azure portal. This will redirect to Ledgy Sign-on URL where you can initiate the login flow.
108+
109+
* Go to Ledgy Sign-on URL directly and initiate the login flow from there.
110+
111+
#### IDP initiated
112+
113+
* Click on **Test this application** in Azure portal and you should be automatically signed in to the Ledgy for which you set up the SSO.
114+
115+
You can also use Microsoft My Apps to test the application in any mode. When you click the Ledgy tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Ledgy 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).
116+
117+
## Additional resources
118+
119+
* [What is single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
120+
* [Plan a single sign-on deployment](../manage-apps/plan-sso-deployment.md).
121+
122+
## Next steps
123+
124+
Once you configure Ledgy 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).

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1439,6 +1439,8 @@
14391439
href: learnupon-tutorial.md
14401440
- name: Lecorpio
14411441
href: lecorpio-tutorial.md
1442+
- name: Ledgy
1443+
href: ledgy-tutorial.md
14421444
- name: Lenses.io
14431445
href: lensesio-tutorial.md
14441446
- name: Lessonly

0 commit comments

Comments
 (0)