Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
feat-rt-recovery-codes
55126d9b feat: add repository layer implementation of recovery codes
15 minutes ago by grvijayan
Succeeded
feat-rt-recovery-codes
55126d9b Merge 468665a61285fb925d67d67a0b5d3c97895ac38d into 3b74b86dc411efec24592f7ab12a9e431c78d195
16 minutes ago by grvijayan
Failed
dependabot/npm_and_yarn/dev-25dd90c1a9
2 hours ago
Failed
next16
dc89a92d in memory swr cache
3 hours ago by peintnermax
Succeeded
qa
3 hours ago
Succeeded
next16
dc89a92d Merge 7f5d27d21a72d988eaf0ff6a0fb81dd1b9ec370c into 3b74b86dc411efec24592f7ab12a9e431c78d195
3 hours ago by peintnermax
Succeeded
next16
3 hours ago
Succeeded
main
3b74b86d fix(login): check for primary auth methods on user discovery (#11689) # Which Problems Are Solved - Currently, if a user has only secondary authentication methods (like TOTP) configured but no primary authentication method (Password, Passkey, or IDP), the login flow fails to handle them correctly, resulting in an unhelpful "user not found" error when they attempt to log in. - These users are not correctly prompted to set up a primary authentication factor, leaving them in a state where they cannot successfully authenticate. # How the Problems Are Solved - Updated `sendLoginname` to evaluate if a user has an active primary authentication method (`AuthenticationMethodType.PASSWORD`, `PASSKEY`, or `IDP`. If they lack a primary method, the flow now correctly redirects them into the verification/invite process rather than falling through the method checks and returning a generic error. - Updated `sendVerification` to replace the empty `authMethodTypes` array check with a specific check for primary authentication methods. Now, after completing email/invite verification, users who do not have a primary authentication method are explicitly redirected to `/authenticator/set` to set one up.
3 hours ago by pull[bot]
Succeeded
main
8ec1e986 Merge 3b74b86dc411efec24592f7ab12a9e431c78d195 into 0261536243e500dccfd8c7f547d592c822478327
3 hours ago by pull[bot]
Failed
qa
3 hours ago
Failed
qa
3 hours ago
Failed
qa
3 hours ago
Succeeded
next16
3 hours ago
Succeeded
main
3b74b86d fix(login): check for primary auth methods on user discovery (#11689) # Which Problems Are Solved - Currently, if a user has only secondary authentication methods (like TOTP) configured but no primary authentication method (Password, Passkey, or IDP), the login flow fails to handle them correctly, resulting in an unhelpful "user not found" error when they attempt to log in. - These users are not correctly prompted to set up a primary authentication factor, leaving them in a state where they cannot successfully authenticate. # How the Problems Are Solved - Updated `sendLoginname` to evaluate if a user has an active primary authentication method (`AuthenticationMethodType.PASSWORD`, `PASSKEY`, or `IDP`. If they lack a primary method, the flow now correctly redirects them into the verification/invite process rather than falling through the method checks and returning a generic error. - Updated `sendVerification` to replace the empty `authMethodTypes` array check with a specific check for primary authentication methods. Now, after completing email/invite verification, users who do not have a primary authentication method are explicitly redirected to `/authenticator/set` to set one up.
4 hours ago by pull[bot]
Succeeded
main
bfa3ca71 Merge 3b74b86dc411efec24592f7ab12a9e431c78d195 into 0261536243e500dccfd8c7f547d592c822478327
4 hours ago by pull[bot]
Succeeded
main
08cd1f80 Merge 54095b64b108a8e5b5031629397ae218bc47ccd4 into ab0f045499d93797d13a7d46a6e4984cb1b46a9f
4 hours ago by pull[bot]
Succeeded
main
3b74b86d fix(login): check for primary auth methods on user discovery (#11689) # Which Problems Are Solved - Currently, if a user has only secondary authentication methods (like TOTP) configured but no primary authentication method (Password, Passkey, or IDP), the login flow fails to handle them correctly, resulting in an unhelpful "user not found" error when they attempt to log in. - These users are not correctly prompted to set up a primary authentication factor, leaving them in a state where they cannot successfully authenticate. # How the Problems Are Solved - Updated `sendLoginname` to evaluate if a user has an active primary authentication method (`AuthenticationMethodType.PASSWORD`, `PASSKEY`, or `IDP`. If they lack a primary method, the flow now correctly redirects them into the verification/invite process rather than falling through the method checks and returning a generic error. - Updated `sendVerification` to replace the empty `authMethodTypes` array check with a specific check for primary authentication methods. Now, after completing email/invite verification, users who do not have a primary authentication method are explicitly redirected to `/authenticator/set` to set one up.
4 hours ago by pull[bot]
Succeeded
main
880f74fc Merge 3b74b86dc411efec24592f7ab12a9e431c78d195 into 0261536243e500dccfd8c7f547d592c822478327
4 hours ago by pull[bot]
Succeeded
main
3b74b86d fix(login): check for primary auth methods on user discovery (#11689) # Which Problems Are Solved - Currently, if a user has only secondary authentication methods (like TOTP) configured but no primary authentication method (Password, Passkey, or IDP), the login flow fails to handle them correctly, resulting in an unhelpful "user not found" error when they attempt to log in. - These users are not correctly prompted to set up a primary authentication factor, leaving them in a state where they cannot successfully authenticate. # How the Problems Are Solved - Updated `sendLoginname` to evaluate if a user has an active primary authentication method (`AuthenticationMethodType.PASSWORD`, `PASSKEY`, or `IDP`. If they lack a primary method, the flow now correctly redirects them into the verification/invite process rather than falling through the method checks and returning a generic error. - Updated `sendVerification` to replace the empty `authMethodTypes` array check with a specific check for primary authentication methods. Now, after completing email/invite verification, users who do not have a primary authentication method are explicitly redirected to `/authenticator/set` to set one up.
5 hours ago by peintnermax
Succeeded
main
5 hours ago