Testing Date: 09 April 2026
BUG Details:
Test Case 1: Request an OTP for registration or password reset, restart the backend server before using the OTP, and then attempt to verify using the same OTP.
Expected Output:
OTP requests should remain valid until their expiry time, or be stored in a persistent/shared storage so that backend restarts do not invalidate them.
Actual Output:
All pending OTPs are lost after a backend restart, causing OTP verification or password reset to fail even if the OTP has not expired.
BUG Report Date: 09 April 2026
Has the bug been fixed? No
Date of BUG fixing: N/A
Any other comment:
This is a reliability issue and may also cause problems in multi-instance deployments where consistent OTP validation is required.
Testing Date: 09 April 2026
BUG Details:
Test Case 1: Request an OTP for registration or password reset, restart the backend server before using the OTP, and then attempt to verify using the same OTP.
Expected Output:
OTP requests should remain valid until their expiry time, or be stored in a persistent/shared storage so that backend restarts do not invalidate them.
Actual Output:
All pending OTPs are lost after a backend restart, causing OTP verification or password reset to fail even if the OTP has not expired.
BUG Report Date: 09 April 2026
Has the bug been fixed? No
Date of BUG fixing: N/A
Any other comment:
This is a reliability issue and may also cause problems in multi-instance deployments where consistent OTP validation is required.