---
title: SSO
slug: docs/sso
createdAt: 2026-05-01T01:45:36.322Z
---

## Jomablue SSO Quick Start

Jomablue supports user login via a SAML2.0-based SSO Identity Provider (Okta, Azure AD, Onelogin, Jumpcloud, etc.).

##

Setup steps

### 1. Contact Jomablue

Request SSO enablement and tell Jomablue which email domain(s) should enforce SSO login. They will provide you with the URLs and X509 certificate needed to configure your Identity Provider. Email support\@jomablue.com with these details to initiate the process.

### 2. Create a SAML2 app in your Identity Provider

In your IdP admin console, create a new custom SAML2 integration and populate the fields with the values provided by Jomablue - each IdP labels these fields differently:

| **Field in IdP**                                                                                            | **URL**                                                          |
| ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| Entity ID / Audience URI<br />SP Entity ID / SP Issuer URL                                                  | https\://\<instance>.jomablue.com/saml2/\<tenant\_uuid>/metadata |
| ACS URL / Reply URL / Single Sign On URL / ACS URL / Assertion Consumer Service URL / Recipient / Reply URL | https\://\<instance>.jomablue.com/saml2/\<tenant\_uuid>/acs      |
| Sign On URL                                                                                                 | https\://\<instance>.jomablue.com/saml2/\<tenant\_uuid>/login    |
| Logout URL (SLO only)                                                                                       | https\://\<instance>.jomablue.com/saml2/\<tenant\_uuid>/sls      |

:::BlockQuote
Not all fields are required by every Identity Provider.
:::

### 3. Configure attribute mapping

Set the application username to email. Also map name attributes — either a single full\_name value, or separate first\_name and last\_name attributes from your IdP.

### 4. Send your IdP details back to Jomablue

Once the SAML2 integration is created, your IdP will generate its own URLs and X509 certificate (or an XML metadata file containing all of this). Send these back to Jomablue via the same channel they used to contact you.

### 5. Jomablue completes setup

Jomablue will notify you when SSO is live. Your portal login page will change to display only an email address field -  that's your confirmation that SSO has been enabled.

## Logging in

Once SSO is active, users can log in via either method:

**Jomablue-initiated login** — The user navigates to the portal login page, enters their email address, and is redirected to authenticate with the IdP. After authenticating, they are directed to the events list.

**IdP-initiated login** — The user clicks the Jomablue icon from their IdP's Apps screen and is taken directly into the portal.

## User provisioning

### First owner user

If your instance does not yet have an owner-level user, the nominated owner should log in via SSO first. Once they have logged in as a portal-level user, notify Jomablue and they will elevate the account to owner/support-level access.

### Additional users via SCIM

Jomablue's SSO integration supports SCIM. Users granted access to Jomablue in your IdP are automatically provisioned as portal-level users — no separate account creation required. To elevate a user above portal-level access, an owner-level user can edit their user record in Jomablue.

