Skip to content
Dashboard
Theme
Theme

SSO

Single sign-on with SAML 2.0 and OIDC, exposed to your app as one OAuth-style flow: authorize, token, profile. This section explains the flow, how sign-ins are routed and what the normalised profile contains.

View Markdown

OhAuthCat brokers SAML 2.0 and OIDC sign-ins into one authorization-code flow. Your application redirects the browser to the broker, exchanges the returned code on its server and receives a normalized profile.

Start with how the flow works, choose routing options, and decide how to map profiles into your own users. The Node and Python examples keep PKCE and state on the server.

SSO proves an identity; your application decides whether that identity may join a tenant, what it may do and how long its session lasts. Existing authentication systems remain responsible for their own sessions.

A hosted test IdP is not available yet.

Inspect sign-in history and timelines, discover normalized attributes, and understand database outage behavior.

Configure sign-in policies and JIT and role rules when your application needs the corresponding admission and assignment controls. Applications still own their sessions and enforce the returned hints. IdP-initiated sign-in is off by default and binds a confirmed handoff to the application’s normal PKCE flow.

For SAML, follow the guarded signing-key rotation workflow rather than replacing certificates without a tested rollback path.