Single Sign-On (SSO)
An identity arrangement that lets a user authenticate through a shared authority and access multiple applications without separate sign-ins.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/single-sign-on/
01What it means
Single sign-on (SSO) centralizes authentication so multiple relying applications accept identity assertions from an identity provider. Protocols such as OpenID Connect or SAML establish federation; each application still maintains its own session and authorization policy.[1][2]
Each relying application validates the assertion, applies its own authorization, and creates its own local session.
02Why it matters
SSO can reduce password proliferation, centralize stronger authentication and offboarding, and simplify access. It also concentrates dependency and compromise risk in the identity provider and its recovery processes.
03When to use it
Use SSO when several applications share a user population or external organizations need federation. A standalone low-risk product may not justify the operational complexity, and local emergency access may still be necessary for critical systems.
04How it works
- Establish trust, identifiers, redirect endpoints, keys, claims, and assurance expectations between applications and an identity provider.
- Redirect an unauthenticated user to the identity provider.
- Authenticate the user there or reuse an eligible provider session.
- Return a protected, audience-bound assertion to the application.
- Validate the assertion, map the account, apply local authorization, and create a local session.
- Coordinate deprovisioning, key rotation, incident response, and logout expectations.
05A practical example
A company connects its support, analytics, and deployment tools to one identity provider. Employees use phishing-resistant MFA once, while each tool maps the trusted identity to separate local roles and session lifetimes.
06Where it breaks
SSO does not mean one shared application session or common authorization. Provider outages can block many services, compromise has a broad blast radius, and logout, account linking, and lifecycle synchronization remain difficult.
Common mistakes
- Assuming SSO automatically centralizes application permissions.
- Matching accounts by mutable email without safe linking rules.
- Skipping issuer, audience, signature, replay, and time validation.
- Providing a weak recovery route that bypasses the identity provider's assurance.
07Sources
- OpenID Connect Core 1.0OpenID Foundation · Technical specificationOpenID Connect Core 1.0
- Digital Identity Guidelines: Federation and AssertionsNIST · Government standardDigital Identity Guidelines: Federation and Assertions