// troubleshooting guide · leapsome

Leapsome SSO Not Working (Okta, Azure AD, Google)

Status
Workaround available
platforms:
Web
updated:
November 17, 2026
reports:
2
Method
how we research
Share

RUNBOOK · leapsome/sso-not-working6 FIXES

// quick answer

Leapsome SAML SSO fails mostly because the user isn't assigned to the Leapsome app in the identity provider, the IdP email differs from the Leapsome email, or the SSO Login URL or certificate was pasted wrong. A 404 usually means the Entity ID was pasted instead of the SSO URL.

Most likely fix: Assign the user to the Leapsome app in your IdP

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Assign the user to the Leapsome app in your IdP

    1. 01Open the Leapsome app in Okta, Entra ID, OneLogin or Google Workspace
    2. 02Add the user or their group to the app assignments
    3. 03Set up an automated rule so new joiners get access
    Did this fix it?
  2. FIX 2Match the email and account status

    1. 01Check the user exists in Leapsome with the same email as in the IdP
    2. 02Make sure they received an invitation or are active
    3. 03On Azure AD, consider just-in-time provisioning so profiles are created at first login
    Did this fix it?
  3. FIX 3Fix the SSO Login URL (404 error)

    1. 01In Google Workspace copy the 'SSO URL', not the 'Entity ID'
    2. 02Paste it into the 'SSO Login URL' field in Leapsome's SSO settings
    3. 03For Okta use 'View SAML setup instructions' to get the correct Login URL
    Did this fix it?
  4. FIX 4Re-paste the certificate

    1. 01For Azure AD paste the full Base64 certificate into 'Certificate'
    2. 02For Okta copy only the alphanumeric part between the <ds:X509Certificate> tags
    3. 03Save and test with one user
    Did this fix it?
  5. FIX 5Check Azure AD identifiers

    1. 01Set Identifier (Entity ID) to https://www.leapsome.com
    2. 02Set Reply URL to the 'Reply URL' shown in your Leapsome SSO settings
    3. 03Use the Login URL from the 'Set up Leapsome' section
    Did this fix it?
  6. FIX 6Switching IdPs

    1. 01Complete the new IdP setup in Leapsome (logins switch to it immediately)
    2. 02Disable the old SAML app so users aren't sent there
    3. 03Tell users before the switch
    Did this fix it?

Symptoms

Users don't see the SSO option, get a 404 or error after the IdP redirect, or new joiners can't sign in.

Why it happens

  • C-01User not assigned or granted access to the Leapsome app in Okta, Entra ID (Azure AD), OneLogin or Google Workspace
  • C-02IdP email doesn't match the Leapsome account email
  • C-03User has no invited or active Leapsome account and JIT provisioning is off
  • C-04Entity ID pasted into the 'SSO Login URL' field (404 error)
  • C-05Certificate pasted incompletely or with the XML tags
  • C-06Company moved to a new IdP; Leapsome supports only one SAML IdP at a time

// this guide also covers

  • leapsome sso error
  • leapsome okta sso
  • leapsome azure ad sso
  • leapsome saml 404

Still not working?

If Leapsome keeps failing, you're not alone. See every Leapsome problem users report or the alternatives people switch to.

Done fighting Leapsome? Our small team builds your own Leapsome alternative, or any software you need: web, mobile, games, desktop. Price agreed together.

Talk to us

Watch Leapsome Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

Other Leapsome errors

All 13 Leapsome errors and fixes →