V2 email for password setup
Hi Team, I have migrated to zitadel v2 API from v1 to avoid storing password. In v2 we can control sending email to set password, but in the verification mail it is asking for password to be set.
How to avoid this? I don't want the user initialization or password set to be automated during user creation. I want it to be separately done by triggering API.
18 Replies
hey @Kanimozhi Set
email.isVerified: true and omit any password in create API call.Yes, I have tried like that only. Is that a correct approach?
Thanks for your response @Rajat
hey @Kanimozhi yes ofc, this should solve the problem that you are looking for 🙂 . Or did I miss anything?.
No just to confirm I asked.
Hi @Rajat ,I am converting v1 API's to v2 API where I am facing an issue with v2 API, I am unable to to hit create user getting "Method not allowed" even after upgrading to version v2.60.0. You can refer the screenshot attached above.
hi @Kanimozhi please omit
/new
The one you are using here is different API @Rajat , the one I have shared in different. This one is working but deprecated, so I was trying to use the new one.
hi @Kanimozhi thanks for pointing that out, I have multipule endpoints running, hence the mistake :), can you please link the doc here that you followed for this endpoint?.
Thanks
Sure @Rajat
You can refer this,
https://zitadel.com/docs/apis/resources/user_service_v2/user-service-create-user
ZITADEL Docs
Create a new human or machine user in the specified organization.
May be my selfhosted zitadel version v2.60.0 is an issue?
Also during user creation, to avoid sending email you refered me to use email.isverified as true right? If we use it we can't initialize user again because it is saying like it is already initialized.
In v2 API, always the user status is active, that is why we are getting like this I guess.
can you pls upgrade to
v3.3.0 if possible?Initially we had v2.46.0 which only supports cocroachDB, We have users created in there. Current version we have updated that v2.60.0 supports both cocroach and postgressDB. So, we used same cocroachDB in that. But v3.3.0 only supports postgress right @Rajat ?
@Rajat Will the DB Migration is easy to handle? It will be helpful if there is any video.
hi @Kanimozhi everything is listed here https://github.com/zitadel/zitadel/issues/9414
and here's the walkthrough https://zitadel.com/docs/self-hosting/manage/cli/mirror
Thanks @Rajat , let me go through this.