damienbod/AspNetCoreOpenIddict — OpenIddict with Angular and Blazor WASM BFF OpenID Connect Code Flow with PKCE clients and ASP.NET C…

Description and use

**Brief Summary**
AspNetCoreOpenIddict (damienbod) is a sample implementation that combines OpenIddict with Angular and Blazor WASM BFFs to deliver a full OpenID Connect Code Flow with PKCE for ASP.NET Core APIs. It gives developers a ready‑made, end‑to‑end authentication and authorization stack that can be dropped into new or existing micro‑service back‑ends, accelerating the delivery of secure APIs.

**Value**

• **Reuse‑first**: By providing a proven OpenIddict‑based identity server, BFF, and client libraries, teams avoid reinventing the same OAuth2/OIDC plumbing for every project.
• **Consistency**: The same patterns (PKCE, BFF, token validation) are enforced across Angular, Blazor WASM, and ASP.NET Core, helping to standardize security across the organization.
• **Speed to market**: With the authentication flow already wired, developers can focus on business logic and API features, shortening the time needed to ship new services.

**Practical Adoption Path**

1. **Evaluate** – Clone the repo and run the Docker‑compose or local launch scripts; the solution includes a reference Angular app, a Blazor WASM BFF, and an ASP.NET Core API.
2. **Customize** – Replace the sample domain models, configure your own external identity providers (e.g., Azure AD, IdentityServer), and adjust client IDs/secrets.
3. **Integrate** – Point your existing APIs to the provided token‑validation middleware, and swap the sample front‑ends with your own UI code.
4. **Test & Harden** – Run the built‑in integration tests, add your own security tests (e.g., token revocation, scopes), and update CI pipelines.

**Production Readiness**

• **Activity & Adoption**: 389 ★, 82 forks, recent commits (last update 2026‑05‑14), and multiple topics indicate an active community.
• **Architecture**: Leverages well‑maintained libraries (OpenIddict, ASP.NET Core, Microsoft Identity) and follows current best practices (PKCE, BFF).
• **Risk Assessment**: No major licensing or security red flags detected, though a final review of the open‑source license and maintainer responsiveness is advised before a full production rollout.

Overall, AspNetCoreOpenIddict is a high‑readiness OSS candidate for teams that need a turnkey, standards‑compliant OIDC solution for .NET back‑ends and modern SPA/WASM front‑ends.

Problem

damienbod/AspNetCoreOpenIddict helps teams reuse service infrastructure instead of rebuilding common backend pieces.

Outcome

High for an OSS candidate: recent activity, adoption, and ecosystem signals are strong enough for a serious pilot.

Workflow

• ship API services faster
• reuse backend infrastructure
• standardize service patterns

Evidence

OpenIddict with Angular and Blazor WASM BFF OpenID Connect Code Flow with PKCE clients and ASP.NET Core APIs

Source