otp local to db storing and addition lockout error message display#6
Open
PareekshithPalat wants to merge 1 commit intofynmanoj:develop-v1.9.1from
Open
otp local to db storing and addition lockout error message display#6PareekshithPalat wants to merge 1 commit intofynmanoj:develop-v1.9.1from
PareekshithPalat wants to merge 1 commit intofynmanoj:develop-v1.9.1from
Conversation
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.
Latest Fix
1) OTP LOCAL TO DB STORING
Instead of storing the generated OTP inside the local system, it now stores the OTP inside the database "m_otp_store".
Once the OTP is used by the user, the otp automatically gets removed from the Database.
2) FIX FOR THE GENERIC ERROR DISPLAY
Previously in the code, when the user gets locked out after the password was changed, it usually throws a generic error message rather than mentioning the real cause.
Changed the generic message to the appropriate error message to notify the user that the lockout period hasn't ended yet.
The message shows the following: