liveBook · Manning

Federated identity integration

Also called federation

Federated identity integration is an arrangement in which a system or organization trusts another identity domain to authenticate identities and provide identity or authorization information.

How 4 Manning books explain it

Kubernetes for Developers

Identity federation is an integration pattern that lets an external identity provider authenticate identities for another system.

How it is used
Connects external developer identities to Kubernetes RBAC so permissions can reference authenticated Users and Groups.
How deep it goes
Explains the integration purpose and group-based bindings, but defers identity-provider setup and configuration details.
Examples
Uses GKE Google users, Google Groups for RBAC, and individual-user versus group role bindings as concrete cases.
What you can do after
Evaluate how an external identity system can supply Kubernetes RBAC subjects and when group bindings can simplify administration.

Read how Kubernetes for Developers explains federated identity integration →

Authorization in Action

Federated identity is an identity model in which organizations trust one another to exchange authentication results and identity attributes so that one organization can provide identity services to another.

How it is used
Connects organizational identity providers to relying parties so external services can authenticate users and receive agreed attributes.
How deep it goes
Explains roles, protocols, contracts, claims, and operational limits, while deferring protocol internals.
Examples
Uses benefits-provider access, Google-based sign-up, tenant OIDC, claim mapping, and external contractor access scenarios.
What you can do after
Operate/configure federated access by connecting IdPs, mapping stable claims, and governing exchanged attributes.

Read how Authorization in Action explains federated identity integration →

Fundamentals of Cybersecurity

Federated identity management is an arrangement in which organizations share trusted identity and authentication information across system or organizational boundaries.

How it is used
Enables access across independent organizations or domains through trusted identity systems, without requiring users to create new credentials.
How deep it goes
Traces authentication through signed-token issuance and validation to application authorization decisions.
Examples
Uses EU-to-U.S. domain access and social login, and names SAML assertions and OpenID Connect ID tokens.
What you can do after
Understand how trusted identity providers support cross-domain access while target applications retain authorization decisions.

Read how Fundamentals of Cybersecurity explains federated identity integration →

MongoDB 8.0 in Action, Third Edition

Federated identity management is a model in which an external identity provider manages identities and enables authentication across multiple relying services.

How it is used
Provides centralized Atlas UI authentication through an organization-managed identity provider.
How deep it goes
Explains the IdP-based model and responsibility boundaries but does not provide provider-specific configuration steps.
Examples
Uses Okta, GitHub, Google, Ping Identity, and Microsoft Entra ID as external identity-provider examples.
What you can do after
Operate Atlas UI authentication through an external identity provider while managing authorization with Atlas roles.

Read how MongoDB 8.0 in Action, Third Edition explains federated identity integration →

Also covered in

What to know first

Related concepts

Questions about federated identity integration

What is federated identity integration?

Federated identity integration is an arrangement in which a system or organization trusts another identity domain to authenticate identities and provide identity or authorization information.

Which Manning books explain federated identity integration?

Kubernetes for Developers, Authorization in Action, Fundamentals of Cybersecurity and MongoDB 8.0 in Action, Third Edition.

What should I know before learning federated identity integration?

Manning books that teach federated identity integration usually introduce authentication, openid connect, authorization and claim first.

What is the difference between federated identity integration and single sign-on?

Federated identity integration is an arrangement in which a system or organization trusts another identity domain to authenticate identities and provide identity or authorization information. Single sign-on is an authentication arrangement in which one authentication event enables a user to access multiple applications or services without signing in separately to each.

What is federated identity integration a kind of?

Federated identity integration is a kind of authentication. Authentication is the process of verifying the claimed identity of a user, service, device, or other entity.

What is federated identity integration also called?

Federated identity integration is also called federation.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.