IdentityServer4

I wonder how much it was ever actually attempted to get more community involvement? At least as of few months back IdentityServer4 was not planning on updating the project for .Net 6. This led to Microsoft updating the ASP.NET templates to point use the new, not-FOSS IdentityServer. Seems like a situation like this, or bug fixes, or etc could have prompted community contribution from companies relying on the project. Frankly, the decision to not update the FOSS project for .Net 6 or accept PRs.. Adds some flavor to the situation: https://github.com/IdentityServer/IdentityServer4/issues/535... .

Is there a technical reason why Microsoft doesn’t use IdentityServer4 with its implementation of the OpenId Connect and Oauth2 technologies. https://github.com/IdentityServer/IdentityServer4. They seem to be pushing it quite hard in Visual Studio and it appears to be designed for this very use case (cross domain authentication). Or do even they think it’s too overkill for GitHub ;)

If you package one of the IdentityServer4[1] quickstarts with e.g. Docker you'll get a comparable result. [1]: https://github.com/IdentityServer/IdentityServer4

If you need to implement your own OIDC/OAuth I highly recommend Identity Server 4[1]. I've used it in production and it was fairly painless to get up going. It's .NET based & battle-tested. It has lots of samples on GitHub to show you how to get going for the various flows (which they even walk you through in their docs) and has a quickstart UI so you've got something you can brand quickly to give users a contiguous login experience. However, if you can manage not to host your own (don't want to mess with it), I recommend either Auth0[2] or the one of the AWS/Azure solutions mentioned elsewhere. [1]https://github.com/IdentityServer/IdentityServer4 [2]https://auth0.com/