Hi @thegoldenegg, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Zitadel Release Versions and Roadmap(2) : Contains roadmap information for various SDKs including Go, Ruby, and Python SDK plans, but doesn't specifically mention .NET SDK updates.
You might want to click the "Ask for help" button to tag a team member who can provide more specific information about .NET SDK update plans.
This has been haunting me for far too long. I have been asking this consistently in the Discord chat for the past 3 months. It seems like .NET SDK has been almost abandoned. As Zitadel approaches the V5 release; and deprecate the V1 API's, there is still no documentation on initializing the V2 Clients using a service user. My company is already looking into adopting KeyCloak or any other Redhat product which seems to be more .NET friendly @thegoldenegg
Hello there, We are struggling to find a way to initialize the V2 clients, as part of the v4 release of Zitadel. Any chance for a small working snippet? Regards, Ville
Hi Rajat! Thanks for the reply. Please express my sincere dissatisfaction that for an SDK of over 350K downloads you are not willing to support it and extend it with the further enhancements of zitadel v4, and upcoming v5. This is really bothersome for us .NET developers. And I will be looking for alternatives for Zitadel as right now this is quite a bottleneck for us
Moi @VilleFTW, thank you for your patience with this one. The SDK that you've linked to is maintained by a third-party. We've been focusing efforts to gradually move our SDKs under our own umbrella.
It's a tricky situation since the upstream maintainers seem to have largely abandoned the project and the one we're working on will probably only materialise after the turn of the year. Our new set of SDKs are built atop ConnectRPC are designed to be rather streamlined across all the major ecosystems. This is one of the core reasons we aren't porting over third party SDKs under our umbrella as they would be a burden to maintain. I
If you are able to hang tight for a little bit, we will try to see if there is any way we can get around this. Again, thank you for this feedback and rest assured, we're working on this one.
Thanks for the update! Looking forward to seeing Zitadel take over the .NET SDK and finally see it being updated. I saw one of the comments of the repo owner saying that he's in the talks with you. I'd greatly appreciate an update whenever that happens https://github.com/smartive/zitadel-net/issues/1005
Hey, This SDK has been dormant in the last months and no Major updates were done to support the new endpoints, or deprecated endpoints, are there any plans on updating this SDK to support the last ...