Identity provider
An identity provider is a system that authenticates users or other entities and supplies identity information or authentication assertions to relying applications and services.
ASP.NET Core in Action, 3e
A third-party identity service is an externally operated identity provider that supplies authentication and identity-management capabilities to applications.
- How it is used
- Centralizes authentication and user management for applications and APIs instead of repeating those responsibilities in each service.
- How deep it goes
- Explains the redirect-and-token flow and selection tradeoffs, but defers provider-specific integration steps to provider documentation.
- Examples
- Uses named third-party services, a shared-provider architecture, and a photo-printing service requesting access to Facebook photos.
- What you can do after
- Evaluate/understand when to delegate sign-in to a third-party provider rather than manage users in an application's own database.
Read how ASP.NET Core in Action, 3e explains identity provider →
Effective Platform Engineering
An identity provider is a system that authenticates entities and supplies identity or authorization information to relying applications and services.
- How it is used
- Connects authentication and team-based authorization so developers can access platform tools, infrastructure and custom APIs.
- How deep it goes
- Explains the intermediary design and a device-authorization flow, but defers a complete comparison of membership implementations.
- Examples
- Uses GitHub teams, CircleCI permissions, an Auth0 configuration exercise and a CLI device-login flow.
- What you can do after
- Operate/configure it by connecting authentication to team claims and issuing credentials for CLI access to platform resources.
Read how Effective Platform Engineering explains identity provider →
Software Security for Developers
An identity provider is a system that authenticates identities and provides identity information to relying applications or services.
- How it is used
- Centralizes authentication so multiple applications can provide single sign-on without separately managing user credentials.
- How deep it goes
- Explains responsibilities, actors, tokens, and authorization-code exchanges, then demonstrates configuration without deeply teaching framework internals.
- Examples
- Uses workplace applications, Google sign-in, token issuance, and a Spring authorization-server configuration as concrete examples.
- What you can do after
- Configure and trace an IdP-backed authorization-code flow, including client registration, redirects, token issuance, and endpoint protection.
Read how Software Security for Developers explains identity provider →
.NET in Action, Second Edition
An identity provider is a service that authenticates users and supplies identity and authorization metadata to client applications.
- How it is used
- Offloads user-account management to external providers while APIs authenticate requests by validating bearer tokens.
- How deep it goes
- Explains OpenID Connect delegation, JWT verification, discovery documents, and ASP.NET Core configuration, while deferring the specification’s broader history.
- Examples
- Uses Microsoft, Facebook, X, Auth0, Okta, Azure AD, Swagger UI, JWT bearer configuration, and an authorized CatalogController.
- What you can do after
- Configure ASP.NET Core JWT bearer authentication, protect controllers, and operate Swagger UI with an external provider.
Read how .NET in Action, Second Edition explains identity provider →
Secure APIs
An identity provider is a service that authenticates identities and issues identity or authorization artifacts to relying clients.
- How it is used
- Outsources application login and supplies tokens for identity and API authorization.
- How deep it goes
- Explains the OIDC flow and token-validation integration, including discovery, JWKS keys, claims, and signing algorithms.
- Examples
- Uses Gmail and GitHub login, authorization endpoints, discovery metadata, authorization codes, and JWKS key selection.
- What you can do after
- Apply via OIDC to delegate login, obtain tokens, and validate protected API requests.
MongoDB 8.0 in Action, Third Edition
An identity provider is a service that authenticates users and supplies verified identity information to relying applications or services.
- How it is used
- Centralizes user authentication for Atlas UI access and federated login across multiple online services.
- How deep it goes
- Defines federated authentication, names supported providers, and identifies configuration responsibilities without detailing provider setup steps.
- Examples
- Uses Okta, GitHub, Google, Ping Identity, and Microsoft Entra ID as external provider examples.
- What you can do after
- Configure federated Atlas UI authentication while retaining organizational control over credentials and assigning access through roles.
Read how MongoDB 8.0 in Action, Third Edition explains identity provider →
Architecting an Apache Iceberg Lakehouse
An identity provider is a system that authenticates users or services and supplies their identities and authorization context to other systems.
- How it is used
- Centralizes authentication and authorization across applications, catalogs, storage, and hybrid or multicloud environments.
- How deep it goes
- Explains federation, policy integration, and authorization patterns, but stops short of protocol or provider implementation detail.
- Examples
- Names Azure Active Directory, Okta, Auth0, Google Identity, Active Directory, OpenLDAP, and 389 Directory Server.
- What you can do after
- Operate/configure centralized access policies across storage and catalogs using federated identities and role or attribute controls.
Read how Architecting an Apache Iceberg Lakehouse explains identity provider →
Build Python Web Apps with Streamlit
An identity provider is a service that authenticates users and supplies identity information to relying applications.
- How it is used
- Delegates application authentication to an external OIDC service instead of maintaining local passwords and hashes.
- How deep it goes
- Explains provider setup, credentials, redirects, user inspection, and logout, but not OIDC protocol internals.
- Examples
- Uses Google, Microsoft, Okta, and Auth0 as providers and demonstrates st.login, st.user, and st.logout.
- What you can do after
- Operate/configure Streamlit authentication with an OIDC provider and inspect the authenticated user.
Read how Build Python Web Apps with Streamlit explains identity provider →
Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu
An identity provider is a system that authenticates identities and issues identity assertions or tokens to relying systems.
- How it is used
- Connects external platforms to cloud identities for passwordless continuous-delivery authentication.
- How deep it goes
- Explains provider registration, authentication versus authorization, identity mapping, and trust restrictions through Terraform and workflow listings.
- Examples
- Uses GitHub Actions and Spacelift integrations, AWS provider registration, certificate fingerprints, IAM roles, and workflow permissions.
- What you can do after
- Configure an OIDC provider and connect external workflows to restricted AWS roles or Azure service principals.
Grokking Web Application Security
An identity provider is a service that authenticates users and supplies identity assertions or authentication services to other applications.
- How it is used
- Delegates application sign-in to trusted third-party or organization-run authentication services.
- How deep it goes
- Explains OAuth/OpenID callbacks and SAML metadata, ACS URLs, and signing certificates without detailing protocol internals.
- Examples
- Uses Facebook login through Ruby OmniAuth and a SAML service-provider callback arrangement.
- What you can do after
- Apply it via OAuth/OpenID or SAML integration by registering an application, handling callbacks, and configuring provider metadata.
Read how Grokking Web Application Security explains identity provider →
Authorization in Action
A central identity provider is a service that centrally manages digital identities and supplies authentication or identity information to relying applications or other systems.
- How it is used
- Centralizes authentication and identity attributes so relying applications can grant access across organizational boundaries.
- How deep it goes
- Explains accounts, authentication, attributes, protocols, and trust agreements, but defers protocol implementation details.
- Examples
- Uses employer-to-benefits-provider federation, Google account sign-up, and tenant-controlled identity for a collaboration platform.
- What you can do after
- Evaluate federated architectures by separating identity ownership, application reliance, protocol exchange, and data-sharing governance.
Read how Authorization in Action explains identity provider →
Building Distributed Applications that Work
An identity provider is a system that authenticates principals and supplies identity information and access-related assertions to applications.
- How it is used
- Coordinates shared authentication across applications in an Aspire security scenario.
- How deep it goes
- Explains the redirect-and-token sign-in flow at a high level, without detailing IdP implementation.
- Examples
- Illustrates Google account reuse and a protected-page redirect that returns an authentication token.
- What you can do after
- Evaluate/understand how an IdP enables SSO and fits into security for Aspire-hosted applications.
Read how Building Distributed Applications that Work explains identity provider →
Related concepts
- single sign-onused by · 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.
- federated identity integrationused by · Federated identity integration is an arrangement in which systems or organizations trust identity and authentication assertions exchanged across their boundaries.
- security tokenproduces · A security token is a credential or assertion presented to a service to convey authenticated identity, authorization, or session information.
- tokenproduces · A token is a discrete unit of text, such as a word, word fragment, character, or symbol, represented and processed as an element by a language model.
- Microsoft Entra IDused by · Microsoft Entra ID is Microsoft's cloud-based identity and access-management service for authenticating users, applications, and services and controlling their access to resources.
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.