Import human users with the v2 API not working as expected
Environment: Zitadel Cloud
Version: v4.3.3
We currently use the v1 APIs to create human users. The call to
The issue is that the link that the user receives by mail uses the "raw" instance domain and not the custom domain, which makes it look weird/unprofessional.
The v2 endpoint for user creation
The verification email (when it gets sent) uses the human-friendly custom domain for links (yay !), but doesn't fill the same use case as the v1 initialization email, in my opinion.
Is there any way to use the v2 APIs and have the initialization email sent with a link that uses a custom domain ?
Version: v4.3.3
We currently use the v1 APIs to create human users. The call to
/management/v1/users/human/_import/management/v1/users/human/_import works as expected and the user receives an initialization email if the email address is not marked as verified or if no password is set.The issue is that the link that the user receives by mail uses the "raw" instance domain and not the custom domain, which makes it look weird/unprofessional.
The v2 endpoint for user creation
/v2/users/new/v2/users/new doesn't send an initialization email, and no verification email is sent either (which I assume is a bug). The verification email can be sent with a separate API call (email sending is properly configured and otherwise works correctly).The verification email (when it gets sent) uses the human-friendly custom domain for links (yay !), but doesn't fill the same use case as the v1 initialization email, in my opinion.
Is there any way to use the v2 APIs and have the initialization email sent with a link that uses a custom domain ?
