added realisation of password reset#325
Merged
Merged
Conversation
This was
linked to
issues
Jun 24, 2025
AndreyDot
approved these changes
Jun 24, 2025
|
This file contains hidden or 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
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.


✅ Functionality overview:
Added two new API endpoints:
POST /api/account/forgot-password
Accepts an email address
Generates a secure reset token using Identity
Sends a reset link via email in the format:
https://localhost:5002/reset-password?token=&email=
POST /api/account/reset-password
Accepts token, email, and new password
Verifies token and resets the password via UserManager.ResetPasswordAsync
Since there is no frontend yet, follow these steps to test the reset:
Use Swagger or Postman to call:
POST /api/account/forgot-password
{
"email": "your_email@example.com"
}
You will receive a reset link via email (from the no-reply Gmail account).
Open the link, copy the token and email from the URL parameters.
Important:
The token in the URL is URL-encoded.
You must decode it before using in the next request.
Use this site to decode the token:
👉 https://www.urldecoder.org/
Call:
CHECK LIST