Federated single sign-on (SSO) is an authentication system where users log in once to access multiple systems across different organizations. It uses identity federation protocols to share authentication data securely.
Federated SSO creates trust relationships between organizations using standardized protocols like SAML, OAuth, or OpenID Connect. When a user logs in to their home organization, that authentication is trusted by partner organizations.
For example, an employee at Company A authenticates through their company portal. When they click a link to access a service at Company B, their credentials are verified through the federation without requiring a second login.
| Protocol | Use Case | Security Features |
|---|---|---|
| SAML | Enterprise applications | XML-based, supports encryption |
| OAuth 2.0 | Web/mobile applications | Token-based, limited scope |
| OpenID Connect | Consumer-facing services | Identity layer on OAuth |
A non-obvious application is in academic research collaborations, where scientists from different institutions need access to shared computing resources without compromising institutional security policies.
The primary advantage is reduced password fatigue for users. According to Gartner, federated SSO can reduce help desk calls about password resets by up to 60%. It also enhances security by centralizing authentication and reducing credential exposure.
However, it requires careful implementation to avoid creating single points of failure. The 2021 SolarWinds attack demonstrated how federated systems can become targets if not properly secured.
Many confuse federated SSO with centralized SSO. While both reduce login prompts, federated SSO maintains separate identity providers, whereas centralized SSO uses a single identity repository for all applications.
Another common mistake is assuming all federated systems use the same protocol. In reality, organizations often implement hybrid solutions using multiple protocols based on specific requirements.