Static `Client ID` id for OIDC configuration
Current Zitadel APIs support static (passed-in) IDs for some entities, but does not do so for others. For example Users can have custom
userId provided trough API, but an Application Client only has a dynamic one (generated by Zitadel instance). This poses some issues in cases where we have an event-driven system, that utilizes Zitadel APIs. We can't create static events (seeds) for dynamic ids. Those are only produced as "side effects". Have you considered to use static (passed-in) ids for all entities in Zitadel or maybe this issue came up in any Zitadel team discussions?4 Replies
it is planned to allow sending the id on a create object request from the api version 2
Indeed it's possible to set id when creating objects. However in case of Applications, there's still ClientId that gets generated. Would it be possible to be able to set it during creation and bulk import as well?
hi @wpiekutowski_n welcome to the server
The current API endpoints do not support setting a custom client ID during application creation - the client ID is always generated by zitadel and returned in the response.
Hi. That is my conclusion as well. I resorted to some SQL UPDATEs as a workaround, but it would be really great if you could support this functionality.