Solutions Integration

Identity providers

Enterprise sign-in connections are configured per organization under Settings → Integrations. Presets fill in the right endpoints and attribute mappings for the providers most customers use; any other SAML or OpenID Connect provider works from its metadata.

app.lumoauth.dev
The integrations hub with its section tabs

What connects

SAML and OpenID Connect presets

OKOkta MIMicrosoft Entra ID GOGoogle Workspace ONOneLogin JUJumpCloud PIPing Identity AUAuth0 KEKeycloak ANAny SAML 2.0 identity provider ANAny OpenID Connect provider

Directories

LDLDAP ACActive Directory

Marketplace listings documented

OKOkta Integration Network MIMicrosoft Entra app gallery GOGoogle Workspace SAML catalog AWAWS Marketplace AZAzure Marketplace

How LumoAuth solves it

Inbound SAML

Paste the provider's metadata, choose the NameID format and signing options, map attributes. Docs

app.lumoauth.dev
Adding a SAML identity provider

Inbound OpenID Connect

Enter the discovery URL and client credentials; claims map to roles and groups. Docs

app.lumoauth.dev
Adding an OpenID Connect provider

LDAP and Active Directory

Bind over TLS; bind credentials are encrypted at rest. Docs

app.lumoauth.dev
LDAP connection

Outbound: LumoAuth as the identity provider

Sign users into SAML-only applications. Docs

Which plan you need

One enterprise connection on Developer and Pro, ten on Business with per-connection overage. LDAP is on Business. Acting as a SAML identity provider is an add-on on Pro and included in Business.

See all plans and add-ons

Documentation

Ship passwordless sign-in this week. Put guardrails on your agents today.

The Developer plan is free for 10,000 monthly users and ten agents, with no card. Everything speaks open standards, so moving in or out is a config change.