IdentityServer
Keycloak
ASP.NET Identity
DotNetOpenAuth
ASP.NET SAML
Authelia
Auth0
OneLogin
IndieAuth
OAuth
OpenID
Portier
humanID
Facebook Connect
myOpenID
IndieLogin
IdentityServer IndieAuthBased on our record, IdentityServer should be more popular than IndieAuth. 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.
Its deprecated in favor of Duende Identityserver which introduced a license model. Source: over 1 year ago
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
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
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
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
IndieAuth[1] is a slick DNS-based approach. Maybe offering that as a service would be a nice alternative. I point my DNS to you, and you handle authentication for everything that uses IndieAuth. If you go away or I don't like what you're doing then I can point my DNS to someone else offering that service and I retain the same DNS identity, and ability to use it to login anywhere I've set it up as my identity.... - Source: Hacker News / over 2 years ago
This is interesting but doing it the other way around - HN using something like IndieAuth[0] to verify user account identities without holding PII on the site itself - might be even more useful. [0]https://indieauth.com/. - Source: Hacker News / over 3 years ago
Keycloak - Open Source Identity and Access Management for modern Applications and Services.
OAuth - OAuth is an open standard for authorization. It allows users to share their private resources (e.g.
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.
OpenID - OpenID is a safe, faster and easier way to log in to web sites.
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.
Portier - An email-based, passwordless authentication service that you can host yourself.