Enterprise SSO · OpenID Connect

One sign-in.
Every customer's
identity provider.

This is a live SSOJet demo. Sign in and your own company identity provider authenticates you — SSOJet returns a verified identity, this site stores it in a signed server session, and you land on a dashboard showing exactly what came back.

Protocol
OIDC
Scopes
openid email profile
Session
HTTP-only
Authorization code flowLive

GET /authorize → code + state

POST /oauth2/token → id_token

GET /userinfo → claims

The round trip

Four steps, one integration, every customer.

Nothing here is simulated. Each step below is the code path this site actually runs when you press sign in.

01

Redirect to SSOJet

The sign-in button sends the browser to your SSOJet project's /authorize endpoint with a random state value that is tied to this browser.

02

Their identity provider authenticates

SSOJet routes the user to whichever enterprise IdP their company has connected — Okta, Entra ID, Google Workspace, and so on.

03

The code is exchanged server-side

SSOJet redirects back with a one-time code. The server exchanges it for tokens using the client secret, which never touches the browser.

04

A signed session begins

Verified claims are written into an HTTP-only cookie with an HMAC signature. Every later request is trusted without re-checking with SSOJet.

Integration sandbox

The part you write once.

Switching between identity providers is an SSOJet configuration change, not a code change. Toggle to compare the surface area.

This site's flow
// after: one integration, every identity provider
const config = await oidc.discovery(
  new URL(process.env.SSOJET_ISSUER),
  process.env.SSOJET_CLIENT_ID,
  process.env.SSOJET_CLIENT_SECRET
);

app.get("/login", (req, res) => {
  res.redirect(oidc.buildAuthorizationUrl(config, {
    redirect_uri: CALLBACK_URL,
    scope: "openid email profile",
    state,
  }));
});

What changes per customer

  • Identity provider

    Configured in SSOJet's admin portal

  • Certificates

    Rotated by the customer's IT team

  • Attribute mapping

    Set in SSOJet, not in code

  • Your deployment

    Nothing to redeploy

Claims

The identity that comes back.

SSOJet normalises every identity provider into the same set of claims, so your application never has to parse a vendor-specific payload.

id_token · sample payloadShown until you sign in
  • subusr_01H8XK2Q7ZJ9M4Tfrom SSOJet
  • emailpriya.nair@acme.examplefrom SSOJet
  • namePriya Nairfrom SSOJet
  • isshttps://acme.auth.ssojet.comfrom SSOJet
  • audapp_8fJ2kLmQfrom SSOJet
  • exp1763318400from SSOJet

After a real sign-in this table fills with the live claims returned by your identity provider.

Configuration

What this deployment needs from SSOJet.

These values live in the app's server environment. The client secret never reaches the browser; the redirect URI must match exactly.

Issuer

https://<your-project>.auth.ssojet.com

Your SSOJet project's login domain

Client ID

Registered application in SSOJet

Sent with every authorization request

Client secret

Stored server-side only

Used for the code exchange, never exposed

Redirect URI

/api/ssojet/callback

Add this exact URL in SSOJet

Scopes

openid email profile

Minimum needed for identity

Response type

code

Authorization code flow