Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
- ABP Framework version: v4.2.0
- UI type: Angular / MVC
- DB provider: EF Core / PostgreSQL
- Tiered (MVC) or Identity Server Seperated (Angular): yes
- Exception message and stack trace:
- Steps to reproduce the issue:
Will the Duende IdentityServer be supported as well in the future? As you probably know, the open source IdentityServer will be essentially replaced by Duende IDentityServer in the long run. Would be nice to have some comittment towads Duende from your side.
7 Answer(s)
-
0
Hi @dweinand, @hikalkan has raised an Issue for this issue, and there is currently no confirmed support for Duende.
-
0
Only recently discovered this. Switching from free OS to multi-thousands per year is a real dick move IMO. I suspect they've created the new company simply to avoid possible legal action.
Is it not likely that V4 will simply get forked? For that matter could ABP not fork it and bundle with their own Admin UI since that's already part of the package? Seems like a golden opportunity if you could.
I've heard good things about Firebase Auth which is free or near free, or Azure AD B2C? Maybe some kind of adapter module?
-
0
Thanks for the pointer @Moyaoxiang. Just to be sure, the Github link points towards the open source project of abp, right?
For us, the integration with IdentityServer that is currently available in abp was one of the drivers to get an abp premium license. As we will most likely not move away from it for our business, and most likely will move over to Duende, we might be interested in comittment (or not) for the commercial apb version. But we are in the early phase of getting to know abp. If we have a better understanding we might be able to answer this question on our own.
But still, some official statement into this direction might be helpful. :)
-
0
Only recently discovered this. Switching from free OS to multi-thousands per year is a real dick move IMO. I suspect they've created the new company simply to avoid possible legal action.
Well. I wouldn't say it’s such a move. It's a "niche" product, that creates a high workload that is/was mostly handled by two persons. Dominik and Brock. They did this year’s long as a side project, spent a lot of effort to maintain the project, and support the community for free. As the product solves a real problem, in a sensitive part of the IT I'm really surprised why so many people are offended as they try now to make a living out of their work. What's wrong with that?
And honestly, I guess most of the people that are using it in a commercial setup are happy with this move, as there is now finally a responsible entity to talk to. If you spent time and money in integrating it in whatever product you have and cannot afford the new licenses, it's a bad situation for sure. Not trying to play that down. But calling them out doing a d**** move is probably not the nicest way of saying: Thank you for all your hard work, and the free ride for now.
Don't get me wrong. I'm not criticizing you or your work in any way. But IMHO support requests in here should not be hijacked by venting off against some decisions you don’t agree with. Especially as there are alternatives to IdSrv available. Yes, they come at the cost of change.
If to blame, then blame Microsoft for not including a proper mainstream solution in their defaults. And hope that Duende will succeed, so that Microsoft will not have another target to make their d**** move against open source and community projects in general.
Is it not likely that V4 will simply get forked?
What holds you back in doing so if it is that important to you? But not part of this discussion either.
-
0
Its a bit rich to complain about my very brief opening sentence and then write a small blog post on why I'm wrong and should go write my own identity server.
If you're going to push ABP to add a dependency on a commercial product costing thousands a year then you can expect pushback from those that have to pay for their own costs.
- With limited users IS5 will die a slow death.
- MS may well implement something now. (BTW. I'll start blaiming MS when they start charging for .net6)
- If a V4 fork emerges I hope that will be supported instead of V5.
- We're also a two man company and didn't envisage further costs.
- Other options like an Azure/Firebase/Amazon adapter should be considered if possible (I've no idea if it is.)
-
0
why I'm wrong and
Never said or implied that.
should go write my own identity server
Same. You could fork it, not go and write your own, if it is important enough to you or your business.
If you're going to push
I don't want to push anything. We are just a paying abp customer and want to know if a commercial product (abp commercial) is going to support a product that turns commercial in the future (Duende IdSrv). All I wanted to explain in my comment is a possible point of view on why it makes sense that the go commercial, and that this not a perfect solution for everybody. If you feel offended. Sorry, never was my intention.
from those that have to pay for their own costs
Sorry, but how does your (personal?) frustration or opinion helping me in this discussion again?
Anyway, if this is how commercial support requests are handled. Well. Let's have think about using abp again I guess.
-
0
Sorry, but how does your (personal?) frustration or opinion helping me in this discussion again?
How does it harm you? Support gave you your answer. I wrote one short followup objecting to ABP becomming dependent on an expensive commercial product, which I'm sure it won't, and you're threatening to rethink your use of the platform! Grow up.
I'm ending here before we have a Godwins Law moment.
