VCST-781: Publish two different events when changing password #2780
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.
Description
Previously, when a user changed their password, the platform would publish the
UserPasswordChangedEvent
event twice: once for the operation itself, and once for the detected changes to the user properties.This PR introduces a separate event for the
change password
operation - theUserChangedPasswordEvent
.So, now there are three events related to the password change:
UserResetPasswordEvent
- user has reset their passwordUserChangedPasswordEvent
- user has changed their passwordUserPasswordChangedEvent
- password has been changed for whatever reason. This event is published for bothreset password
andchange password
operations.References
QA-test:
Jira-link:
https://virtocommerce.atlassian.net/browse/VCST-781
Artifact URL: