Software Alternatives, Accelerators & Startups

IdentityServer VS DotNetOpenAuth

Compare IdentityServer VS DotNetOpenAuth and see what are their differences

This page does not exist

IdentityServer logo IdentityServer

An open-source, standards-compliant, and flexible OpenID Connect and OAuth 2.x framework for ASP.NET Core

DotNetOpenAuth logo DotNetOpenAuth

DotNetOpenAuth is a free-to-use compiled library that comes with the real support to your site visitor to login with the help of openIDs via getting control of the ASP.NET control onto the page.
  • IdentityServer Landing page
    Landing page //
    2023-02-03
  • DotNetOpenAuth Landing page
    Landing page //
    2021-07-03

IdentityServer features and specs

  • Open Source Foundation
    IdentityServer is built on an open-source foundation. It has been widely used and developed by a community, ensuring transparency, reliability, and continuous improvements.
  • Comprehensive Protocol Support
    It supports industry standards such as OpenID Connect and OAuth 2.0, which are essential for authentication and authorization processes.
  • Customizability
    IdentityServer offers high levels of customizability, allowing developers to tailor authentication and authorization features to specific application needs.
  • Enterprise-Ready
    Designed to handle complex enterprise scenarios with robust performance and scalability options suitable for large-scale applications.
  • Strong Security Features
    Includes several security mechanisms to protect sensitive data, such as secure token storage and advanced encryption options.
  • Comprehensive Documentation
    Provides extensive documentation and resources, helping developers to implement and troubleshoot the server effectively in their systems.

Possible disadvantages of IdentityServer

  • Licensing Cost
    Since its transition from IdentityServer4 to a non-OSS model under Duende Software, organizations need to purchase a license for commercial use, impacting budget-conscious projects.
  • Complexity
    Can be complex to set up and configure properly, especially for teams that are new to security protocols like OAuth and OpenID Connect.
  • Maintenance Overhead
    Requires ongoing maintenance and updates to ensure security and compatibility with evolving protocols, which can be resource-intensive.
  • Potential Overhead for Small Projects
    May be overkill for smaller projects or teams that do not require robust authentication systems, where simpler solutions might suffice.
  • Community vs. Commercial Transition
    The switch from a community-driven open-source project to a commercial product may alienate previous users who relied on its open-source nature.

DotNetOpenAuth features and specs

  • Comprehensive Support
    DotNetOpenAuth supports multiple OAuth and OpenID versions, making it versatile for different authentication scenarios.
  • Security Features
    The library includes built-in features to handle security concerns, such as token encryption and secure transmission protocols.
  • Community and Documentation
    DotNetOpenAuth has a history of strong community support and extensive documentation, which can be helpful in learning and troubleshooting.
  • Integration with .NET Framework
    The library is designed to integrate seamlessly with the .NET framework, making it easy to implement in existing .NET applications.

Possible disadvantages of DotNetOpenAuth

  • Complexity and Learning Curve
    The library offers many features, which can make it complex and difficult to learn for newcomers.
  • Maintenance and Updates
    There have been concerns about the frequency of updates and maintenance, which might affect long-term usability and compatibility with new standards.
  • Limited .NET Core Support
    DotNetOpenAuth primarily targets the .NET Framework, with limited support for .NET Core, which may necessitate alternatives for modern applications.
  • Performance Overhead
    The extensive feature set can introduce performance overhead, particularly in scenarios that require lightweight solutions.

IdentityServer videos

Federated Identity: An intro to OAuth2, Open Id Connect & Duende IdentityServer 5 | Anthony Nguyen

More videos:

  • Review - There's an IdentityServer in my API project - Anders Abel

DotNetOpenAuth videos

No DotNetOpenAuth videos yet. You could help us improve this page by suggesting one.

Add video

Category Popularity

0-100% (relative to IdentityServer and DotNetOpenAuth)
Identity And Access Management
Network & Admin
45 45%
55% 55
Identity Provider
100 100%
0% 0
Tool
0 0%
100% 100

User comments

Share your experience with using IdentityServer and DotNetOpenAuth. For example, how are they different and which one is better?
Log in or Post with

Reviews

These are some of the external sources and on-site user reviews we've used to compare IdentityServer and DotNetOpenAuth

IdentityServer Reviews

10+ Open-source Single-Sign On (SSO) Solutions
If you are looking for a certified and complaint system to OpenID Foundation, with .Net technologies, then IdentityServer is your answer.
Source: medevel.com
Top 5 Open Source Single Sign-On Software In the Year 2021
IdentityServer is an open source free single sign-on software. It is a cross-platform framework based on OpenID Connect and OAuth 2. Further, this open source software provides central authentication and authorization capabilities for multiple applications. It supports federated identities, multiple flows, and API authorization. Moreover, this self hosting software enables...

DotNetOpenAuth Reviews

We have no reviews of DotNetOpenAuth yet.
Be the first one to post

Social recommendations and mentions

Based on our record, IdentityServer should be more popular than DotNetOpenAuth. It has been mentiond 7 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

IdentityServer mentions (7)

  • Identity server 4
    Its deprecated in favor of Duende Identityserver which introduced a license model. Source: over 1 year ago
  • How does cookie based authentication work?
    Tokens usually have a lifetime and they are separate from the user's authentication principals like username and password. Unless you are rolling your own form of token provider (not something that would be recommended) the token creation is handled for you. Take a look at https://identityserver4.readthedocs.io/en/latest/ or if your organization makes under 1M in income a year the free version of what Identity... Source: over 2 years ago
  • ImageSharp leaving the .NET Foundation due to licensing change
    I think Duende (Identity Server) handled the situation pretty well. https://duendesoftware.com/products/identityserver > Standard License Pricing. - Source: Hacker News / over 2 years ago
  • Why is authentication such a sh*t show with .NET 6?
    He's referring to IdentityServer 3/4, which was open sourced, and was not owned by Microsoft. That 3rd party is commercializing their work (and to be fair, it's a lot of work) as https://duendesoftware.com/products/identityserver , and has a different commercial licensing model. Source: almost 3 years ago
  • Show HN: Open-Source Identity Server Written in Go (Ory Kratos)
    I think "Identity Provider" is more correct, no? "IdentityServer" is the name of a specific IdP implemented in .NET (formerly OSS as https://identityserver4.readthedocs.io/en/latest, and now as a more commercial form as Duende IdentityServer: https://duendesoftware.com/products/identityserver). - Source: Hacker News / almost 3 years ago
View more

DotNetOpenAuth mentions (1)

  • OpenID Provider open source library
    But if the OpenID server would be for a intranet or low number of requests, you can go ahread (in my opinion) and the post also recommends http://dotnetopenauth.net/ because has a OpenID provider and samples. Source: over 2 years ago

What are some alternatives?

When comparing IdentityServer and DotNetOpenAuth, you can also consider the following products

Keycloak - Open Source Identity and Access Management for modern Applications and Services.

ASP.NET Identity - ASP.NET Identity is a membership-based software system designed for the authentication and authorization of the users via building an ASP.NET application.

OAuth - OAuth is an open standard for authorization. It allows users to share their private resources (e.g.

Auth0 - Auth0 is a program for people to get authentication and authorization services for their own business use.

ASP.NET SAML - ASP.NET SAML is an open-source authentication utility that has been used for exchanging authentication and authorization data between the channels.

Okta Workforce Identity - Okta Workforce Identity is utility software for enterprises that provides a new way of work that enable your employees, contractors, and partners to use technology on any device.