damienbod
commented
3 years ago Hi @derbl4ck
No idea 😊. At present, I plan to maintain this till the end of life .NET Core 3.1. After this, it depends. I am waiting to see what Microsoft do with their templates and how Microsoft plan to support OIDC solutions. At present, I see the following solutions possible after the .NET 6 release:
Possible solutions
- KeyCloak (OSS with Apache-2.0 License)
- OpenIddict (OSS with Apache-2.0 License)
- node-oidc-provider (OSS with MIT license)
Possible paid solutions:
- Azure AD (license)
- Auth0 (license)
- Okta (license)
- DuendeSoftware (license) + UI license from partner company
- Gluu (license)
Things like ease of use, dependency risk, cost of maintenance, UI, support, cost to implement, long term perspective for the product, community size, developer team skills will all have to be considered when choosing a post .NET 6 solution.
Greetings Damien
As known since October 1st 2020, the parent project IdentityServer4 will only receive bug fixes and security updates until November 2022. In the future, the developers in the https://github.com/DuendeSoftware/IdentityServer project will continue to develop.
What are the plans for this repo? Will the code be adapted accordingly? How long will there be suitable support here?