How to Configure SSO in the Lumu MSP Portal using JumpCloud

How to Configure SSO in the Lumu MSP Portal using JumpCloud

Learn how to Configure SSO in the Lumu Portal for MSPs using JumpCloud by following this article.

Prerequisites

Before you can configure Single Sign-On (SSO) integration with the Lumu Portal for MSPs using JumpCloud ensure that you have the following:

  • Administrator access to your JumpCloud console.
  • An active communication channel with the Lumu Support team to finalize the setup.
  • The email address of each JumpCloud user that will sign in must match their Lumu MSP Portal for account email.

JumpCloud Setup

1. Log in to the JumpCloud Console and go to Access → SSO Applications.


2. Click Create New Application to start configuring the new application integration.

3. In the Select Application step, use the search box or scroll to Featured Applications. Then select Custom Application.


4. The Custom Application supports SSO with SAML (among other features). Click Next to confirm the selection.


5. In the Select Options step, check Manage Single Sign-On (SSO) and choose Configure SSO with SAML, and leave every other option unchecked. Then, Click Next.


6. In the Enter General Info step, set the Display Label (e.g. SSOLUMU). Optionally add a description and a User Portal image/color. Make sure you check the Show this application in User Portal option.



When finished, click Save Application.

7. You'll see a confirmation message when the application was successfully added. Click Configure Application to complete the SAML setup.


8. Go to the SSO tab. Under Configuration Settings, configure the Service Provider (Lumu) as follows:

Field Value (Customer Portal)
IdP Entity ID SSOLUMU (any stable identifier; this becomes the SAML issuer)
SP Entity ID https://managed.lumu.io/api/v1/users/saml/auth
ACS URL (index 0, Default URL) https://managed.lumu.io/api/v1/users/saml/auth
SAMLSubject NameID The user's email attribute

Key information

  • The SP Entity ID and the ACS URL must be identical to the values above. The SP Entity ID is sent as the SAML Audience; if it doesn't match what Lumu expects, sign-in fails with an audience error.
  • Set the SAMLSubject NameID to the user's email. Lumu identifies the account by the email in the SAML response, so this mapping is required.
  • Client/SP signature is not required for this integration.

When finished, click Save.

7. Go to the Users tab and bind the group(s) whose members should have access to the Lumu MSP Portal (e.g. a static group such as SSOTEST). Then, click Save.


NotesOnly bound users will be able to launch the application and authenticate via SSO.

8. Go the SSO tab, under JumpCloud Metadata, click Export Metadata (or Copy Metadata URL) to download the IdP metadata XML.


9. Send this IdP metadata XML file to the Lumu Support team. Lumu uses it to configure the backend for your company. Once Lumu confirms the backend is configured, the SSO is active and ready to use for your users.

      Get an AI Summary