Replies: 1 comment 1 reply
|
Hi @muhlemmer, Thanks for the transparency in this update — that kind of communication is genuinely appreciated. Since this post is from August 2025, I wanted to ask whether the situation has evolved in the meantime, or whether the thread simply hasn't been updated. Specifically:
The context for asking: we're evaluating Zitadel as the IAM layer for a multi-tenant healthcare SaaS in Switzerland, and the MCP (Model Context Protocol) authorization spec is becoming a relevant factor. Specifically RFC 8707 (Resource Indicators) and RFC 7591 (Dynamic Client Registration) — both of which would need to land in We're not pushing for a commitment, just trying to understand whether to plan around current capabilities or wait for upcoming features. Thanks! |
|
The nature of this post is targeted to features in the library that do not directly contribute to the health of the company. Feature requests / PRs that benefit the product and the company get prioritized.
We've discussed your use-case and are looking into the issues and PRs you've raised.
Yes, they did. However, we're also trying out a new direction of our product, which has our entire team swamped, so we really only pick up tasks that are urgent (security, commercial). I know you or people on your team already reached out us on the commercial part. I would recommend anybody reading this doing the same if a feature request is a commercial dealbreaker. For others I will still ask for your patience. The landscape of software development is changing fast, and as a company we're dedicating our resources to making sure we can keep up. |
Uh oh!
There was an error while loading. Please reload this page.
Hello contributors,
Due to growth of our company, we are currently struggling allocating time for reviews of feature pull requests. Fixes and security updates still get our attention regularly. We are working on resolving the issue by hiring a new IAM engineer, but the process is taking a little longer as expected.
As soon as we get a new IAM engineer as maintainer of this lib, we should be able to start picking up features and do some needed cleanup and refactoring.
Thanks for understanding,
Zitadel staff.
All reactions