How to Add Enterprise SSO to an Emergent App (Server-Side OIDC)
Blog post from SSOJet
Emergent apps can implement enterprise SSO through a server-side OpenID Connect confidential-client flow, keeping the client secret and token exchange on the backend while the browser receives only a signed HttpOnly session cookie. The setup uses SSOJet issuer and client ID settings, a backend callback at `/api/auth/callback`, and a client secret added separately in Emergent’s Secrets settings or backend environment file; the app’s home page indicates whether the secret is configured and displays the redirect URI to register. Preview and published addresses may differ, so each callback must be registered exactly. A suggested first prompt builds sign-in and a dashboard, while a second can route users to organization-specific identity providers using a validated `org` parameter; that feature requires SSOJet’s Business plan. Passkeys and MFA are enabled in SSOJet’s hosted login settings rather than built into the app, and require no changes to the app’s sign-in flow. The article reports that the basic sign-in prompt was tested successfully, while the organization-routing and passkey/MFA prompts were based on SSOJet documentation; it also recommends checking the configured status, callback, hosted login, and browser cookies to verify setup. SSOJet’s Free plan includes sign-in, passkeys, and MFA, while enterprise SSO is priced per connection on the Business plan, with terms subject to confirmation.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Secrets Management | 5 | 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.