OpenIddict

The OpenID Connect stack you'll be addicted to.

What's OpenIddict?

OpenIddict aims at providing a versatile solution to implement OpenID Connect client, server and token validation support 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.

OpenIddict natively supports Entity Framework Core, Entity Framework 6 and MongoDB out-of-the-box and custom stores can be implemented to support other providers.

---

Getting started

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.

---

Compatibility matrix

Web framework version	.NET runtime version	OpenIddict 3.x	OpenIddict 4.x
ASP.NET Core 2.1	.NET Framework 4.6.1	✔️ ℹ️	✔️ ℹ️
ASP.NET Core 2.1	.NET Framework 4.7.2	✔️	✔️
ASP.NET Core 2.1	.NET Framework 4.8	✔️	✔️
ASP.NET Core 2.1	.NET Core 2.1	✔️	❗
ASP.NET Core 3.1	.NET Core 3.1	✔️	✔️
ASP.NET Core 5.0	.NET 5.0	✔️	❗
ASP.NET Core 6.0	.NET 6.0	✔️	✔️
ASP.NET Core 7.0	.NET 7.0	⚠️ ℹ️	✔️
Microsoft.Owin 4.2	.NET Framework 4.6.1	✔️ ℹ️	✔️ ℹ️
Microsoft.Owin 4.2	.NET Framework 4.7.2	✔️	✔️
Microsoft.Owin 4.2	.NET Framework 4.8	✔️	✔️

Warning ASP.NET Core 2.1 on .NET Core 2.1 and ASP.NET Core 5.0 on .NET 5.0 are no longer supported by Microsoft. 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.

Warning OpenIddict 3.x is impacted by a breaking change introduced in ASP.NET Core 7.0 and may require using an AppContext compatibility switch if the application only uses the OpenIddict server feature alone without any other authentication handler registered.

A workaround has been integrated into OpenIddict 4.0 preview5 and using a compatibility switch is no longer necessary on 4.0 preview5 and higher.

For more information, read ASP.NET Core 7.0's default authentication handler fallback breaks OpenIddict.

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.

---

Certification

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

---

Resources

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

• OpenIddict 4.0 preview1 is out by Kévin Chalet
• Introducing the OpenIddict-powered providers by Kévin Chalet
• Introducing the OpenIddict client by Kévin Chalet
• Secure a Blazor WASM ASP.NET Core hosted APP using BFF and OpenIddict by Damien Bowden
• 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:

• ABP Framework OpenIddict module: full-stack Web application framework for .NET
• OpenIddict UI by Thomas Duft: headless UI for managing client applications and scopes
• OrchardCore OpenID module: turnkey OpenID Connect server and token validation solution, built with multitenancy in mind
• P41.OpenIddict.CouchDB by Panos Athanasiou: CouchDB stores for OpenIddict
• pixel-identity by Nishant Singh: Ready to host OpenID Connect service using OpenIddict and ASP.NET Identity with a Blazor-based UI for managing users, roles, applications and scopes with support for multiple databases.

---

Security policy

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.

---

Support

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

---

Nightly builds

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>

Contributors

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:

---

License

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.