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, 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 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:
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.
Tip
This repository contains a dedicated sample specially designed to be used with the OpenID Connect Provider Certification tool and demonstrate that OpenIddict can be easily used in a certified implementation. To allow executing the certification tests as fast as possible, that sample doesn't include any membership or consent feature (two hardcoded identities are proposed for tests that require switching between identities).
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.
Important
With OpenIddict 5.x being now generally available, the previous version, OpenIddict 4.x, stops being supported and won't receive bug fixes or security updates. As such, it is recommended to migrate to OpenIddict 5.x to continue receiving bug and security fixes.
There are, however, two exceptions to this policy:
-
ABP Framework 7.x users will still receive patches for OpenIddict 4.x for as long as ABP Framework 7.x itself is supported by Volosoft (typically a year following the release of ABP 8.x), whether they have a commercial ABP license or just use the free packages.
-
OpenIddict sponsors who have opted for a $250+/month sponsorship are now offered extended support:
- $250/month sponsors get full support for OpenIddict 4.x until June 18, 2024 (6 months).
- $500/month sponsors get full support for OpenIddict 4.x until December 18, 2024 (12 months).
- $1,000/month sponsors get full support for OpenIddict 4.x until December 18, 2025 (24 months).
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.