Aman-Mittal commented on PR #5369:
URL: https://github.com/apache/fineract/pull/5369#issuecomment-3797044864

   I think it would be a good practice if we can implement a limiter on this.
   Like you can use forgot password at certain times. Within a span of
   interval. Like in every 5-10 minutes at a time for single user?
   
   On Sun, 25 Jan, 2026, 10:31 pm Aira Jena, ***@***.***> wrote:
   
   > *airajena* left a comment (apache/fineract#5369)
   > <https://github.com/apache/fineract/pull/5369#issuecomment-3796957318>
   >
   > Seems ok now, but really curious what type of safeguards are implemented
   > in this, Additionally we need to tests for the code coverage
   >
   > Below things are on the safeguards side
   >
   >    - The generated password is time-bound (24 hours). After expiry, it’s
   >    automatically invalid and cannot be used.
   >    - Once the user logs in using the temporary password, they are
   >    required to change it immediately, and the temporary credentials are
   >    cleared.
   >    - Any successful password update (either through this flow or via an
   >    admin action) invalidates the temporary password.
   >    - If email delivery fails, the transaction is rolled back so no
   >    orphaned temporary passwords are stored.
   >    - Password reset requests go through the service layer and are logged,
   >    so the activity is traceable
   >
   > —
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/fineract/pull/5369#issuecomment-3796957318>,
   > or unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/AHV6TAZBOYWXIQOMB2PGVW34ITZHRAVCNFSM6AAAAACSUFDBTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOJWHE2TOMZRHA>
   > .
   > You are receiving this because you commented.Message ID:
   > ***@***.***>
   >
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to