AspNetCore.Identity
Allows storing users inc. passwords in your app, login & acct management, Twitter/FB/social login, etc. docs.microsoft.com/aspnet/core/se…
1/5
AspNetCore.Authentication/Authorization
Base AuthN/AuthZ APIs for using/implementing AuthN schemes (cookie, JWT, OIDC, etc.) & AuthZ rules (roles, policies, attributes, etc.) in your app. docs.microsoft.com/aspnet/core/se…
2/5
MS Identity
Diff. team that owns Azure identity services inc. support for Azure AD, OAuth, OIDC, MS Graph, etc. docs.microsoft.com/azure/active-d…
3/5
IdentityServer (Duende)
3rd-party OSS lib/product for hosting your own IdP server/endpoints. For when you want your own OAuth/OIDC server. Often used in conjunction w/ AspNetCore.Identity duendesoftware.com/products/ident…
4/5
OpenIddict
3rd-party OSS lib for integrating w/ OAuth/OIDC providers and/or hosting your own OAuth/OIDC server. documentation.openiddict.com
5/5
BONUS TWEET
Check out this recently updated MS Learn module for a good overview of using AspNetCore.Identity to host your own user database, customize register/login/manage UI, integrate with social auth, do policy-based AuthZ, etc.
2.1 is 15 months through it's 3 year support lifecycle. That means it certainly has had a bunch of fixes to make it more "stable", but of course those are all in 3.0 too :)
@Nick_Craver@shanselman@mayankdotnet 3.1 will be out shortly (Dec) and will be LTS, giving a fresh 3 year support term. Moving from 3.0 to 3.1 should be trivial.
@Nick_Craver@shanselman@mayankdotnet 3.0 of course has new features that can introduce instability, but it was by far the highest used version during previews we've ever had, and is the fastest adopted version of .NET Core ever by a huge margin. We haven't had to issue a patch due to stability problems so far