Federated Identity
Subject: Computer and Technology noun /ˈfɛd.əˌreɪ.tɪd aɪˈdɛn.tɪ.ti/ 1 definition
- identity-management
- information-security
- access-control
- single-sign-on
-
Definition (noun)
Entry #134 · UpdatedFederated Identity is an identity-management architecture that links a user's electronic identity and attributes across multiple independent security domains, organizations, or applications. Rather than requiring each service to maintain its own credential store and authenticate users directly, a federated system establishes a cryptographic trust relationship between an identity provider (IdP), which verifies the user's identity, and relying service providers (SPs), which accept digitally signed assertions or tokens from that IdP to grant access. Unlike intra-domain single sign-on (SSO), which shares sessions within a single administrative boundary, federated identity extends authentication trust across separate legal or technical entities without exposing underlying passwords to third-party services.
Common Forms
SAML 2.0 Federation: Exchanges digitally signed XML assertions between an identity provider and service providers via browser redirects, serving as the predominant standard for enterprise workforce and business-to-business (B2B) single sign-on.
OpenID Connect (OIDC) Federation: Builds an identity layer over OAuth 2.0 using JSON Web Tokens (JWTs) and RESTful JSON endpoints, making it well suited for modern web applications, mobile clients, and consumer social logins.
WS-Federation: Relies on WS-Trust and Security Token Services (STS) to issue and broker XML-based security tokens across organizational boundaries, remaining common in legacy enterprise environments and Microsoft Active Directory Federation Services (AD FS) deployments.
Example
When an employee at a partner firm opens a third-party cloud analytics portal (
analytics.example.com), the portal redirects their browser to their employer's identity provider rather than asking for a separate password. Once the employee authenticates on their home organization's login page, the identity provider issues a digitally signed SAML 2.0 assertion containing their user identifier and role claims, allowing the analytics portal to create a verified session without ever receiving or storing the employee's password.