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.
10 Replies
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?
Unknown User•2w ago
Message Not Public
Sign In & Join Server To View
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
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
Hey @Raccine any chance there’s an update on this? Thanks!
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
hey @AYEEDITYA looking into it
Thank you!
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 requestI’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.