# Single Sign-On \(SSO\)

An identity arrangement that lets a user authenticate through a shared authority and access multiple applications without separate sign-ins.

- Type: practice
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/single-sign-on/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Establish trust, identifiers, redirect endpoints, keys, claims, and assurance expectations between applications and an identity provider.
2. Redirect an unauthenticated user to the identity provider.
3. Authenticate the user there or reuse an eligible provider session.
4. Return a protected, audience-bound assertion to the application.
5. Validate the assertion, map the account, apply local authorization, and create a local session.
6. Coordinate deprovisioning, key rotation, incident response, and logout expectations.

## A 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.

## Where 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.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/single-sign-on/#visualization-single-sign-on>)

## Sources

1. [OpenID Connect Core 1.0](<https://openid.net/specs/openid-connect-core-1_0.html>) — OpenID Foundation · Technical specification
2. [Digital Identity Guidelines: Federation and Assertions](<https://pages.nist.gov/800-63-4/sp800-63c.html>) — NIST · Government standard

## Related topics

- [OpenID Connect \(OIDC\)](<https://wiki.soroush.uk/topic/openid-connect/>)
- [Authentication](<https://wiki.soroush.uk/topic/authentication/>)
- [Role-Based Access Control \(RBAC\)](<https://wiki.soroush.uk/topic/role-based-access-control/>)
