While I understand the choice by the IdentityServer guys, this is not good news for cloudscribe as we don't want to depend on commercial products or introduce weird license loop holes or exceptions.
I remember a long while back Microsoft started making noise about implementing its own thing for JWT auth something like IdentityServer. I along with others urged them not to put out their own thing that would kill off important open source projects in the .net ecosystem such as IdentityServer. At the time Microsoft then agreed to just use IdentityServer and layer on some code to make it easier to use.
I can only guess and hope that this change will prompt Microsoft to implement something to replace it so that the .net stack can remain open source.
While I understand the choice by the IdentityServer guys, this is not good news for cloudscribe as we don't want to depend on commercial products or introduce weird license loop holes or exceptions.
I remember a long while back Microsoft started making noise about implementing its own thing for JWT auth something like IdentityServer. I along with others urged them not to put out their own thing that would kill off important open source projects in the .net ecosystem such as IdentityServer. At the time Microsoft then agreed to just use IdentityServer and layer on some code to make it easier to use.
I can only guess and hope that this change will prompt Microsoft to implement something to replace it so that the .net stack can remain open source.