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.
• Hollastin: resource owner password credentials demo, with a .NET console acting as the client.
• Imynusoph: refresh token grant demo, with an Angular application 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 Steam 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: implicit flow demo, with an Aurelia JS application acting as the client and two API projects using introspection (Api1) and local validation (Api2).

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

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.

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 [email protected]. 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 make sure you sponsor the project before creating a GitHub ticket. If you're not a sponsor, you can post your questions on Gitter or StackOverflow:

• Gitter: https://gitter.im/openiddict/openiddict-core
• StackOverflow: https://stackoverflow.com/questions/tagged/openiddict

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 https://www.apache.org/licenses/LICENSE-2.0.html for more details.