feat(ums): reset user's password #143
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marlosin
force-pushed
the
feature/ums-reset-password
branch
from
071e9d9
to
fce7137
Compare
KutsenkoA
requested changes
Jan 27, 2020
marlosin
force-pushed
the
feature/ums-reset-password
branch
from
fce7137
to
8196fdc
Compare
marlosin
force-pushed
the
feature/ums-reset-password
branch
from
8196fdc
to
123f2af
Compare
marlosin
force-pushed
the
feature/ums-reset-password
branch
from
123f2af
to
696d1ac
Compare
KutsenkoA
approved these changes
Feb 21, 2020
miss-tique
pushed a commit
that referenced
this pull request
Mar 5, 2020
# [4.8.0](v4.7.0...v4.8.0) (2020-03-05) ### Features * **ums:** reset user's password ([#143](#143)) ([cf0e4a6](cf0e4a6))
|
🎉 This PR is included in version 4.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
In order to change an user's password, the user should know the current one.
What is the new behavior?
Now it's possible to reset an user's password with two steps, first request the reset, then with token change to a new password.
Does this PR introduce a breaking change?