OpenIddict aims at providing a versatile solution to implement an OpenID Connect server and token validation in any ASP.NET Core 2.1 (and higher) application. ASP.NET 4.6.1 (and higher) applications are also fully supported thanks to a native Microsoft.Owin 4.2 integration.

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, read Getting started.

Samples demonstrating how to use OpenIddict with the different OAuth 2.0/OpenID Connect flows can be found in the dedicated repository.

❗ Note: ASP.NET Core 2.1 on .NET Core 2.1 is no longer supported. While OpenIddict 4.x can still be used on .NET Core 2.1 thanks to its .NET Standard 2.0 compatibility, users are strongly encouraged to migrate to ASP.NET Core/.NET 6.0. ASP.NET Core 2.1 on .NET Framework 4.6.1 (and higher) is still fully supported.

ℹ️ 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.

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.

The samples 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).

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

• How to Secure ASP.NET Core Applications with OpenIddict Using Virto Commerce B2B eCommerce: Tech Case Study by Virto Commerce
• OpenIddict 3.0 general availability by Kévin Chalet
• Setting up an Authorization Server with OpenIddict by Robin van der Knaap
• Introducing OpenIddict 3.0's first release candidate version by Kévin Chalet
• OpenIddict 3.0 beta6 is out by Kévin Chalet
• Introducing Quartz.NET support and new languages in OpenIddict 3.0 beta4 by Kévin Chalet
• Introducing localization support in OpenIddict 3.0 beta3 by Kévin Chalet
• 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

OpenIddict-based projects maintained by third parties:

• OrchardCore OpenID module: turnkey OpenID Connect server and token validation solution, built with multitenancy in mind
• OpenIddict UI by Thomas Duft: headless UI for managing client applications and scopes
• P41.OpenIddict.CouchDB by Panos Athanasiou: CouchDB stores for OpenIddict

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

If you want to try out the latest features and bug fixes, there is a MyGet feed with nightly builds of OpenIddict. To reference the OpenIddict MyGet feed, create a NuGet.config file (at the root of your solution):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="nuget" value="https://api.nuget.org/v3/index.json" />
    <add key="openiddict" value="https://www.myget.org/F/openiddict/api/v3/index.json" />
  </packageSources>
</configuration>

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

Special thanks to our sponsors for their incredible support:

• Sébastien Ros
• mridentity
• Andrew
• gustavdw
• Gillardo
• Dovydas Navickas
• Christian Schmitt
• Thomas W
• torfikarl
• Lewis Cianci
• Florian Wachs
• Vasko Poposki
• Sebastian Stehle
• Michael Hochriegl
• sunielreddy
• Communicatie Cockpit
• Keith Turner
• WGMurray
• Thomas Bjallas
• Pablo Pioli
• Michael Calasanz

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.