mirror of
https://github.com/zitadel/zitadel.git
synced 2025-12-07 15:32:02 +00:00
feat: invite user link (#8578)
# Which Problems Are Solved As an administrator I want to be able to invite users to my application with the API V2, some user data I will already prefil, the user should add the authentication method themself (password, passkey, sso). # How the Problems Are Solved - A user can now be created with a email explicitly set to false. - If a user has no verified email and no authentication method, an `InviteCode` can be created through the User V2 API. - the code can be returned or sent through email - additionally `URLTemplate` and an `ApplicatioName` can provided for the email - The code can be resent and verified through the User V2 API - The V1 login allows users to verify and resend the code and set a password (analog user initialization) - The message text for the user invitation can be customized # Additional Changes - `verifyUserPasskeyCode` directly uses `crypto.VerifyCode` (instead of `verifyEncryptedCode`) - `verifyEncryptedCode` is removed (unnecessarily queried for the code generator) # Additional Context - closes #8310 - TODO: login V2 will have to implement invite flow: https://github.com/zitadel/typescript/issues/166
This commit is contained in:
@@ -185,7 +185,8 @@
|
||||
"VE": "Saat pengguna mengubah alamat emailnya, mereka akan menerima email berisi tautan untuk memverifikasi alamat baru.",
|
||||
"VP": "Saat pengguna mengganti nomor teleponnya, mereka akan menerima SMS berisi kode untuk memverifikasi nomor baru.",
|
||||
"VEO": "Ketika pengguna menambahkan Kata Sandi Sekali Pakai melalui metode email, mereka perlu mengaktifkannya dengan memasukkan kode yang dikirimkan ke alamat email mereka.",
|
||||
"VSO": "Ketika pengguna menambahkan One-Time Password melalui metode SMS, mereka perlu mengaktifkannya dengan memasukkan kode yang dikirimkan ke nomor telepon mereka."
|
||||
"VSO": "Ketika pengguna menambahkan One-Time Password melalui metode SMS, mereka perlu mengaktifkannya dengan memasukkan kode yang dikirimkan ke nomor telepon mereka.",
|
||||
"IU": "Ketika kode undangan pengguna dibuat, mereka akan menerima email dengan tautan untuk mengatur metode otentikasi mereka."
|
||||
}
|
||||
},
|
||||
"LOGIN_TEXTS": {
|
||||
@@ -1533,7 +1534,8 @@
|
||||
"PR": "Reset Kata Sandi",
|
||||
"DC": "Klaim Domain",
|
||||
"PL": "Tanpa kata sandi",
|
||||
"PC": "Perubahan Kata Sandi"
|
||||
"PC": "Perubahan Kata Sandi",
|
||||
"IU": "Mengundang Pengguna"
|
||||
},
|
||||
"CHIPS": {
|
||||
"firstname": "Nama yang diberikan",
|
||||
@@ -1553,7 +1555,8 @@
|
||||
"tempUsername": "Nama pengguna sementara",
|
||||
"otp": "Kata sandi satu kali",
|
||||
"verifyUrl": "Verifikasi URL kata sandi satu kali",
|
||||
"expiry": "Kedaluwarsa"
|
||||
"expiry": "Kedaluwarsa",
|
||||
"applicationName": "Nama aplikasi"
|
||||
},
|
||||
"TOAST": { "UPDATED": "Teks Khusus disimpan." }
|
||||
},
|
||||
|
||||
Reference in New Issue
Block a user