IdentityServer transitioning to commercial license

0

I am just curious if any other Cloudscribe users who also depend on the IdentityServer Integration are aware of the transition of IdentityServer to a commercial license (https://leastprivilege.com/2020/10/01/the-future-of-identityserver/) and how they are dealing with the impact in regards to decision making. In my case there is one net new project I was just getting ready to begin where this is making me re-think my implementation and then there is another where a commercial license for the IdentityServer is no big deal. Has anyone integrated an alternative in Cloudscribe such as OpenIddict successfully?

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.

- joe.audette

We will be keeping a close eye on this and reviewing alternatives. In our own client projects and products, like you Mike we have one major scenario where some commercial licensing is no big deal, and another where it could be problematic. And as Joe says we don't want commercial/complex dependencies in the cloudscribe open source libraries.
For anyone who's not read the announcements, note that they say:

This new product will remain open source but will be offered with a dual license (RPL and commercial). The RPL (reciprocal public license) keeps Duende IdentityServer free if you are also doing free open source work. If you are using Duende IdentityServer in a commercial scenario, then a commercial license will be required.

- crispinflower

Answers

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.

The only thing I came across (open source wise) that seems a viable alternative is OpenIddict which is used by OrchardCore, however, I have no idea how stable/viable it is. I definitely do not blame the IdentityServer guys for the decision they made as we all need to pay mortgages/eat, etc.

- mike
0

We will be keeping a close eye on this and reviewing alternatives. In our own client projects and products, like you Mike we have one major scenario where some commercial licensing is no big deal, and another where it could be problematic. And as Joe says we don't want commercial/complex dependencies in the cloudscribe open source libraries.
For anyone who's not read the announcements, note that they say:

This new product will remain open source but will be offered with a dual license (RPL and commercial). The RPL (reciprocal public license) keeps Duende IdentityServer free if you are also doing free open source work. If you are using Duende IdentityServer in a commercial scenario, then a commercial license will be required.

0

Your Answer

Log in Log in to post You can post an answer as guest, but some features may not be available.