# SSO

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](/sso/how-it-works/), choose [routing options](/sso/routing/), and decide how to map [profiles](/sso/profiles/) into your own users. The [Node](/get-started/quickstart-node/) and [Python](/get-started/quickstart-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](/sso/working-with-existing-auth/) remain responsible for their own sessions.

A hosted test IdP is not available yet.

Inspect [sign-in history and timelines](/sso/sign-in-history/), discover [normalized attributes](/sso/attributes/), and understand [database outage behavior](/trust/database-outages/).

Configure [sign-in policies and JIT](/sso/sign-in-policies/) and [role rules](/sso/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](/sso/idp-initiated/) is off by default and binds a confirmed handoff to the application’s normal PKCE flow.

For SAML, follow the guarded [signing-key rotation](/sso/signing-key-rotation/) workflow rather than replacing certificates without a tested rollback path.
