AYEEDITYA
AYEEDITYA4w ago

Creating local user in Zitadel V3

Hey, so I recently upgraded to V3. Everything is well, however, when I create a local user in a specific organization, the user is still only created in the default org. Whys this? And how can I make it so it’s created in the specified organization? Since there is also no way to move a user to a different org.
15 Replies
AYEEDITYA
AYEEDITYAOP4w ago
This only happens when I have enabled to “Use V2 API in Console for User Creation”. If I turn that off then I’m able to create local users in the selected organization. Is this a bug?
Raccine
Raccine4w ago
Hey there @AYEEDITYA! Thanks for reaching out and sorry to hear that you're experiencing this issue. Prior to upgrading to V3, were you experiencing this issue at all?
AYEEDITYA
AYEEDITYAOP4w ago
Hey, no this was not an issue. In fact, if I set the user creation console to use V1 as in my last message, everything is good. But the V2 API console creates local users in the default org regardless of the the active organization
AYEEDITYA
AYEEDITYAOP4w ago
I just tested with creating a service user in a non-default org and those are created in the selected org. But human users are always created in the default org when the feature "Use V2 API in Console for User Creation" is checked. But when disabled, human users are created in the non default org
No description
AYEEDITYA
AYEEDITYAOP3w ago
Hey @Raccine any chance there’s an update on this? Thanks!
Raccine
Raccine3w ago
Hi there! Let me loop in an engineer to take a look at this with you and see why you might be experiencing this - @Rajat Singh
Rajat
Rajat2w ago
hey @AYEEDITYA looking into it
AYEEDITYA
AYEEDITYAOP2w ago
Thank you!
Rajat Singh
Rajat Singh2w ago
hey @AYEEDITYA there could be a Temporary Workaround for now Disable the V2 API toggle to revert to the V1 API. This ensures human users are created in the correct organization and Create service users via the V2 API (if needed) since they are unaffected by this limitation. If using the API directly (not the Console), ensure the org_id field is included in the request body when creating a human user. Here is the request
AYEEDITYA
AYEEDITYAOP2w ago
I’m not planning on using the API anytime soon - console only for now. It’s not a big deal, and switching to V1 works well as I mentioned earlier as did you. So are you confirming this is a bug? Or is it by design? Would like to know how to further move along.
Rajat Singh
Rajat Singh2w ago
hey @AYEEDITYA good morning, I just tested it too , its indeed a bug, you can open an issue , tag this thread and explain your findings. It fails to create a user in a particular org even tho being in the correct org. But the API works without any issue, its just the console.
AYEEDITYA
AYEEDITYAOP2w ago
Okay good to know! Will open an issue
AYEEDITYA
AYEEDITYAOP2w ago
GitHub
[Bug]: User not created in selected org with V2 API frontend · Iss...
Preflight Checklist I could not find a solution in the documentation, the existing issues or discussions I have joined the ZITADEL chat Environment Self-hosted Version 3.2.1 Database PostgreSQL Dat...
Rajat
Rajat2w ago
good day @AYEEDITYA we are working on a fix of this, here's the PR : https://github.com/zitadel/zitadel/pull/9971 hope this helps
GitHub
fix(console): org context for V2 user creation by peintnermax · Pu...
Which Problems Are Solved This PR addresses a bug in Console V2 APIs, specifically when the feature toggle is enabled, which caused incorrect organization context assignment during new user creation.
AYEEDITYA
AYEEDITYAOP2w ago
awesome! Thank you!

Did you find this page helpful?