A flexible and versatile OAuth 2.0/OpenID Connect stack for implementing client, server, and token validation in .NET applications.
OpenIddict is a flexible OAuth 2.0 and OpenID Connect stack for .NET that provides the tools to implement client, server, and token validation features. It solves the problem of adding standards-compliant authentication and authorization to .NET applications without locking developers into a specific vendor or hosted solution.
.NET developers building applications that require custom identity providers, secure API access, or integration with OAuth 2.0/OpenID Connect services, particularly those needing full control over their authentication logic.
Developers choose OpenIddict for its versatility, extensive protocol support, and ability to work across multiple platforms and data stores, offering a robust alternative to commercial identity services while allowing complete customization.
Flexible and versatile OAuth 2.0/OpenID Connect stack for .NET
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements all major OAuth 2.0 and OpenID Connect flows, including code, implicit, hybrid, client credentials, resource owner password, device authorization, and token exchange grants, as explicitly listed in the README.
Offers native support for Entity Framework Core, Entity Framework 6, and MongoDB, with extensibility for custom stores, allowing seamless integration with various database backends.
Can be used in ASP.NET 4.6.2+ and ASP.NET Core 2.3+ web apps, and also in non-web applications on Android, iOS, Linux, Mac Catalyst, macOS, and Windows, as highlighted in the README.
Works with both legacy ASP.NET and modern ASP.NET Core frameworks, providing wide compatibility across different .NET versions and easing migration paths.
Requires writing custom code like authorization controllers to be operational, as admitted in the README, making it unsuitable for teams seeking plug-and-play authentication.
Only the latest stable version is supported for free users; extended support requires sponsorship or ABP Framework integration, which can complicate long-term maintenance for non-paying teams.
Lacks out-of-the-box OpenID Connect certification; developers must implement and run conformance tests on their own deployments, adding to development time and complexity.