This repository contains samples demonstrating how to use OpenIddict with the different OAuth 2.0/OpenID Connect flows.

• Aridka: client credentials demo, with a .NET console acting as the client.
• Balosar: authorization code flow demo, with a Blazor WASM application acting as the client.
• Contruum: conformance tests project using Razor Pages and 2 hardcoded user identities, meant to be used with the OIDC certification suite.
• Dantooine: backend-for-frontend (BFF) Blazor WASM application hosted in ASP.NET Core with Microsoft YARP for downstream API.
• Hollastin: resource owner password credentials demo, with a .NET console acting as the client.
• Imynusoph: refresh token grant demo, with a .NET console acting as the client.
• Matty: device authorization flow demo, with a .NET console acting as the client.
• Mimban: authorization code flow demo using minimal APIs and GitHub delegation for user authentication, with a .NET console acting as the client.
• Velusia: authorization code flow demo, with an ASP.NET Core application acting as the client.
• Weytta: authorization code flow with Integrated Windows Authentication support and a .NET console acting as the client.
• Zirku: authorization code flow demo using minimal APIs with 2 hard-coded user identities, a .NET console and a SPA acting as the clients and two API projects using introspection (Api1) and local validation (Api2).

• Sorgan: console, Windows Forms, Windows Presentation Foundation and Blazor Hybrid clients using GitHub for user authentication.

• Fornax: authorization code flow demo using ASP.NET Web Forms 4.8 and OWIN/Katana, with a .NET Framework 4.8 console acting as the client.
• Mortis: authorization code flow demo using ASP.NET MVC 5.2 and ASP.NET Web API 2.2, with an ASP.NET MVC 5.2 application acting as the client.
• Kalarba: resource owner password credentials demo using OWIN/Katana, ASP.NET Web API 2.2 and the OpenIddict degraded mode.

Looking for additional samples to help you get started with OpenIddict? Don't miss these interesting samples maintained by the community:

• Angular and Blazor samples by Damien Bowden

• Experimental MAUI (WinUI-only) sample by Kévin Chalet

• OIDC Session Management sample by Graham Esau

Unlike many other identity providers, OpenIddict is not a turnkey solution but a framework that requires writing custom code to be operational (typically, at least an authorization controller), making it a poor candidate for the certification program.

While a reference implementation could be submitted as-is, this wouldn't guarantee that implementations deployed by OpenIddict users would be standard-compliant.

Instead, developers are encouraged to execute the conformance tests against their own deployment once they've implemented their own logic.

Security issues and bugs should be reported privately by emailing security@openiddict.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

If you need support, please first make sure you're sponsoring the project. Depending on the tier you selected, you can open a GitHub ticket or send an email to contact@openiddict.com for private support. Alternatively, you can also post your question on Gitter.

Support is only offered for the latest stable version of OpenIddict. There are, however, two exceptions to this policy:

• ABP Framework users receive patches for OpenIddict for as long as ABP Framework itself is supported by Volosoft (typically a year following the release of a major ABP version), whether they have a commercial ABP license or just use the free packages.

• OpenIddict sponsors are offered extended support depending on the selected sponsorship tier:
  • $100/month sponsors get full support for the previous version 1 month following the release of a new major version.
  • $250/month sponsors get full support for the previous version 6 months following the release of a new major version.
  • $500/month sponsors get full support for the previous version 12 months following the release of a new major version.
  • $1,000/month sponsors get full support for the previous version 24 months following the release of a new major version.

OpenIddict is actively maintained by Kévin Chalet. Contributions are welcome and can be submitted using pull requests.

This project is licensed under the Apache License. This means that you can use, modify and distribute it freely. See http://www.apache.org/licenses/LICENSE-2.0.html for more details.