Single sign-on overview
Connect your existing directory so that access to Seylo is granted where you already grant everything else, and revoked the same way.
Supported providers
Section titled “Supported providers”Before you start
Section titled “Before you start”| You need | Why |
|---|---|
admin in Seylo |
SSO configuration is administrator-only |
| Administrative access to your directory | You will create an app registration and, usually, add a claim |
| To know how your roles are expressed | Groups? App roles? A custom claim? This is the part that goes wrong |
Configuration lives under Admin → Single sign-on → Providers in the portal. Choose your identity provider there and the page shows the steps for it: what to create in your provider’s console, the values to copy from Seylo (each with a Copy button, already filled in with your portal’s address), where each value Seylo asks for lives in your provider, and how to test. Once a provider is configured its steps are hidden. Each provider page on this site has the same steps, for reading before you start.
The values you will copy from Seylo
Section titled “The values you will copy from Seylo”| Sign-in with | Values | Example |
|---|---|---|
| Microsoft Entra ID | redirect URI (Single-page application) | https://portal.seylo.in |
| Any other OIDC provider | redirect URI, and the origin for CORS | https://portal.seylo.in/ and https://portal.seylo.in |
| Test tab, optional | test redirect URI | https://portal.seylo.in/api/auth/sso/test/callback |
| SAML 2.0 | SP entity ID, ACS URL, sign-on URL | https://portal.seylo.in/api/auth/saml/<your organisation>/metadata, .../acs, .../login |
The redirect URIs are matched exactly, including the trailing /.
The values you bring back
Section titled “The values you bring back”Never more than three: an identifier for your directory (tenant ID, domain, realm URL or issuer), the client ID, and a client secret, which Seylo stores encrypted and never shows again. Only Google Workspace needs the secret for signing in: Seylo completes Google sign-ins on its server with it (see the client secret). Elsewhere it is optional: with Entra ID it is only for the Test tab’s Sign in for real, and another OpenID Connect provider saved with one has its sign-ins completed on Seylo’s server in the same way. Seylo works out the rest (the discovery URL, the accepted audiences) and shows you what it found before you save.
The one concept to understand first: the tenant key
Section titled “The one concept to understand first: the tenant key”Seylo identifies your organisation from the token’s issuer, plus — where the issuer is not unique to you — a discriminator claim.
That second part exists for one reason: Entra ID gives every directory its own
issuer, but Google Workspace gives every organisation on earth the same
issuer, https://accounts.google.com. The issuer alone cannot tell your
Workspace from anyone else’s.
| Provider | Discriminator | Required? |
|---|---|---|
| Entra ID, single directory | — | No. The issuer already embeds your directory ID |
| Entra ID, multi-tenant app | tid |
Recommended |
| Google Workspace | hd |
Yes |
| Okta | — | No. One issuer per org or authorization server |
| Auth0 without Organizations | — | No |
| Auth0 with Organizations | org_id |
Recommended |
| Keycloak | — | No. One issuer per realm |
Three behaviours follow, and all three are deliberate:
- No discriminator configured → the issuer alone resolves your organisation.
- Configured but absent from the token → rejected. Never “try the other
organisations”, never “use the default”. A Google token with no
hdis a personal Gmail account and must not land in a Workspace organisation. - Present but unmatched → rejected, naming the claim and the value that arrived. It never falls through to another organisation sharing the issuer, and the message names no other organisation.
What Seylo enforces on every sign-in
Section titled “What Seylo enforces on every sign-in”You do not configure any of this; it is worth knowing it is there.
- Signature verified against that issuer’s published keys, fetched over https from a discovery document that must declare the issuer it was served from.
- Only asymmetric algorithms.
HS256andnoneare refused — withHS*the signing key is the client secret, which is not a signature in any useful sense. - Audience checked against your registered audiences; expiry and not-before enforced.
- An unknown issuer is a 401, never a fallback to some default organisation.
- An
(issuer, discriminator)pair already owned by another organisation cannot be taken over. Moving one is an explicit delete then add, because a registration is a trust anchor. - Some issuers are reserved. A SAML entity ID or OpenID Connect issuer
that starts with
local://orbreak-glass://is refused when you save the provider: Seylo writes those itself for its own password and break-glass sign-ins, and no identity provider can sign as them. So is an issuer that Seylo’s own staff sign in through. Enter the entity ID or issuer your provider publishes in its metadata.
For SAML, signature validation uses @node-saml/node-saml rather than
hand-rolled XML handling: it verifies the bytes the signature actually covered
(which is what defeats signature-wrapping attacks) and validates only against
the certificate you configured — never one embedded in the received document.
Recommended order
Section titled “Recommended order”- Register Seylo in your directory and configure the provider here.
- Run test login before telling anyone it works. It shows the complete claim set and says, per value, whether each role mapped and why not.
- Set up role mapping.
- Close self-service signup — see managing users.
- Read break-glass recovery before you need it.