fix(ui): trigger login hooks after reset password #14711
+78
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Added execution of
beforeLoginandafterLoginhooks during the password reset operation inresetPasswordOperation(). These hooks now execute with the same parameters and flow as they do in the standard login operation, ensuring consistent behavior across both authentication paths.packages/payload/src/auth/operations/resetPassword.ts- Added hook execution before and after JWT token generation.Why?
When a user resets their password, the operation performs two phases: updating the password in the database, then automatically logging the user in with a new session and JWT token. However,
beforeLoginandafterLoginhooks were not being triggered during this auto-login phase, creating inconsistent behavior compared to standard login.This caused issues for applications that uses
afterLoginhooks to attach additional cookie (for example).How?
Triggered
beforeLoginandafterLogininresetPassword.ts