Federated identity integration
Federated identity integration is an arrangement in which systems or organizations trust identity and authentication assertions exchanged across their boundaries.
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 →
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 →
Related concepts
- identity provideruses · An identity provider is a system that authenticates users or other entities and supplies identity information or authentication assertions to relying applications and services.
- Security Assertion Markup Languageuses · Security Assertion Markup Language is an XML-based standard for exchanging authentication, identity, and authorization assertions between identity providers and service providers.
- trust frameworkuses · A trust framework is a set of legal, operational, and technical rules that defines how parties exchange and use identity information and the guarantees they provide.
- OAuthuses · OAuth is an authorization framework that enables a client to obtain limited, delegated access to protected resources without receiving the resource owner's credentials.
- single sign-oncontrasts with · 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.
- authenticationkind of · Authentication is the process of establishing or verifying the identity of a user, service, device, or other communicating entity.
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.