ASP.NET Core 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.
- Hollastin: resource owner password credentials demo, with a .NET console acting as the client.
- Imynusoph: refresh token grant demo, with an Angular JS application acting as the client.
- Kalarba: resource owner password credentials demo using OWIN/Katana, ASP.NET Web API and the OpenIddict degraded mode.
- 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).
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 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 http://www.apache.org/licenses/LICENSE-2.0.html for more details.