How to Add Enterprise SSO to a Base44 App (Server-Side OIDC)
Blog post from SSOJet
Base44’s backend functions support a server-side OpenID Connect sign-in flow in which the client secret and token exchange remain on the server, while the browser receives only a signed, HTTP-only session cookie. Setup involves configuring an SSOJet application, registering the exact callback URL, and storing the issuer, client ID, and client secret as Base44 secrets; the callback at `/api/ssojet/callback` verifies state and exchanges the authorization code. For customer-specific enterprise SSO, the login route can accept a validated organization value and pass it to SSOJet, while passkeys and multi-factor authentication are enabled on SSOJet’s hosted login page rather than built into the app. The guide recommends checking that tokens never appear in browser storage or responses and notes that callback mismatches, different preview and production URLs, or missing secrets are common causes of errors. It also states that basic sign-in, passkeys, and MFA are available on SSOJet’s free plan, while enterprise SSO requires a paid plan, with listed per-connection pricing and a startup discount subject to confirmation.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Secrets Management | 15 | 2,152 | 404 | 126 | -30% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.