DotNetOpenAuth
By DotNetOpenAuth
ASP.NET Identity
By aspnet
| DotNetOpenAuth | ASP.NET Identity | |
|---|---|---|
| 1 | 2 | |
| 1,681 | 1,915 | |
| - | - | |
| 0.0 | 0.0 | |
| over 6 years ago | over 5 years ago | |
| C# | C# | |
| - | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DotNetOpenAuth
Posts with mentions or reviews of DotNetOpenAuth.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Easiest way to develop an OIDC provider in .NET Framework
I saw this post from 2012, and it's almost exactly the same situation as ours, but the DotNetOpenAuth repository has been archived since 2019. There is also the IdentityServer project, but IdentityServer3 seems to be the most recent version that still supports .NET Framework (not Core), and it hasn't been updated since 2018.
ASP.NET Identity
Posts with mentions or reviews of ASP.NET Identity.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-03-06.
-
2FA logins with "magic link" style passwordless authentication?
There's nothing wrong with directly getting the user in their flow, the GetTwoFactorAuthenticationUserAsync is just the method that uses a tfa cookie to flow the information in the templates. The obvious caveat is that you would need to be careful to not make it easy to bypass the first/password step, but there's not a lot of ceremony underneath the covers: https://github.com/aspnet/Identity/blob/master/src/Identity/SignInManager.cs#L526
-
What every ASP.NET Core Web API project needs - Part 3 - Exception handling middleware
If you wrap the result into another object like IdentityResult, you should pay the extra heap allocation. For each call, an extra object should be initialized even for the successful operation. If you call an API 100 times with different inputs, how many times an exception may be thrown? So the rate of throwing an exception with the extra object initializing (and heap allocation) is not the same
What are some alternatives?
When comparing DotNetOpenAuth and ASP.NET Identity you can also consider the following projects:
ASP.NET SAML - Very simple SAML 2.0 consumer module for ASP.NET/C#
OAuth
TwoFactorAuth.Net - .Net library for Two Factor Authentication (TFA / 2FA)
Cierge
PwdLess
CodeNode.Identity - An easy implementation for Identity framework for .net applications
IAmRoot NuGet Package - 📦🏴☠️ NuGet package that shows we can run arbitrary code from any NuGet package
Stuntman - Library for impersonating users during development leveraging ASP.NET Identity.
DotNetOpenAuth vs ASP.NET SAML
ASP.NET Identity vs OAuth
DotNetOpenAuth vs TwoFactorAuth.Net
ASP.NET Identity vs Cierge
DotNetOpenAuth vs OAuth
ASP.NET Identity vs ASP.NET SAML
DotNetOpenAuth vs PwdLess
ASP.NET Identity vs PwdLess
DotNetOpenAuth vs CodeNode.Identity
ASP.NET Identity vs TwoFactorAuth.Net
DotNetOpenAuth vs IAmRoot NuGet Package
ASP.NET Identity vs Stuntman