OpenIddict aims at providing a versatile solution to implement an OpenID Connect server and token validation in any ASP.NET Core 2.1, 3.1 and 5.0 application, and starting in OpenIddict 3.0, any ASP.NET 4.x or OWIN application too.

OpenIddict fully supports the code/implicit/hybrid flows, the client credentials/resource owner password grants and the device authorization flow. You can also create your own custom grant types.

OpenIddict natively supports Entity Framework Core, Entity Framework 6 and MongoDB out-of-the-box, but you can also provide your own stores.

Developers looking for a simple and turnkey solution are strongly encouraged to use OrchardCore and its OpenID module, which is based on OpenIddict, comes with sensible defaults and offers a built-in management GUI to easily register OpenID client applications.

To implement a custom OpenID Connect server using OpenIddict, the simplest option is to clone one of the official samples from the openiddict-samples repository:

• Samples for OpenIddict 3.0 can be found in the samples repository.
• Samples for OpenIddict 2.0.1 can be found in the master branch of the samples repository.

The documentation for the latest stable release (2.0.1) can be found in the dedicated repository.

ℹ️ Note: the following features are not available when targeting .NET Framework 4.6.1:

• X.509 development encryption/signing certificates: calling AddDevelopmentEncryptionCertificate() or AddDevelopmentSigningCertificate() will result in a PlatformNotSupportedException being thrown at runtime if no valid development certificate can be found and a new one must be generated.
• X.509 ECDSA signing certificates/keys: calling AddSigningCertificate() or AddSigningKey() with an ECDSA certificate/key will always result in a PlatformNotSupportedException being thrown at runtime.

Looking for additional resources to help you get started with 3.0? Don't miss these interesting blog posts:

• OpenIddict 3.0 beta2 is out by Kévin Chalet
• Introducing OpenIddict 3.0 beta1 by Kévin Chalet
• Adding OpenIddict 3.0 to an OWIN application by Kévin Chalet
• Creating an OpenID Connect server proxy with OpenIddict 3.0's degraded mode by Kévin Chalet

Posts written for previous versions of OpenIddict:

• Implementing an OpenIddict Authorization server: Social Login with GitHub by Jerrie Pelser
• Implementing an OpenIddict Authorization server: A Basic Authorization Server by Jerrie Pelser
• Implementing simple token authentication in ASP.NET Core with OpenIddict by Kévin Chalet
• Bearer Token Authentication in ASP.NET Core by Mike Rousos (for the Microsoft .NET Web Development and Tools blog)
• Creating your own OpenID Connect server with ASOS by Kévin Chalet
• Using OpenIddict to easily add token authentication to your .NET web apps by Josh Comley

Need help or wanna share your thoughts? Don't hesitate to join us on Gitter or ask your question on 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.

Special thanks to the following sponsors for their incredible support:

• David Hamilton from DAM Good Media
• Christopher McCrum from Data Citadel

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.