mirror of
https://github.com/zitadel/zitadel.git
synced 2024-12-13 19:44:21 +00:00
07b2bac463
# Which Problems Are Solved User created through the User V2 API without any authentication method and possibly unverified email address was not able to login through the current hosted login UI. An unverified email address would result in a mail verification and not an initialization mail like it would with the management API. Also the login UI would then require the user to enter the init code, which the user never received. # How the Problems Are Solved - When verifying the email through the login UI, it will check for existing auth methods (password, IdP, passkeys). In case there are none, the user will be prompted to set a password. - When a user was created through the V2 API with a verified email and no auth method, the user will be prompted to set a password in the login UI. - Since setting a password requires a corresponding code, the code will be generated and sent when login in. # Additional Changes - Changed `RequestSetPassword` to get the codeGenerator from the eventstore instead of getting it from query. # Additional Context - closes https://github.com/zitadel/zitadel/issues/6600 - closes https://github.com/zitadel/zitadel/issues/8235 --------- Co-authored-by: Stefan Benz <46600784+stebenz@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| avatar.go | ||
| email_converter.go | ||
| email.go | ||
| idp_converter.go | ||
| idp.go | ||
| information.go | ||
| language.go | ||
| metadata_converter.go | ||
| multi_factor.go | ||
| password_complexity.go | ||
| password.go | ||
| passwordless.go | ||
| permission_converter.go | ||
| permission.go | ||
| phone_converter.go | ||
| phone.go | ||
| policy.go | ||
| profile_converter.go | ||
| profile.go | ||
| refresh_token.go | ||
| server.go | ||
| user_grant.go | ||
| user.go | ||