Closed WillStrohl closed 1 year ago
The correct fix here is as follows:
Email
column in the database should be renamed to Username
. All related code will need to be updated. Code
column in the database should be renamed to ValidationPacket
to make its contents a bit more vague. Email
property. Instead, it should be querying the Username
property. Also, please rename the data table from Upendo_Simple_Auth_VerificationCodes
to Upendo_SimpleAuthVerification
. This should need to be done in both SqlDataProvider files.
Understood! I get to work on this quickly.
Sponsorship
If this request requires additional support (e.g., such as direct email/phone/meeting/development), I have the following interest in helping to sponsor the effot via GitHub Sponsors:
Describe the bug
When I tried testing this, I successfully sent the notification, but then changed the casing of a single character, then attempted to validate the code. An exception was thrown, and I was redirected to the home page.
Software Versions
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There should have been an error message of some kind telling me that the code was not valid. (It is good for this to be case-sensitive.)
Actual behavior
An exception occurred, and I was redirected to the homepage.
Screenshots
If applicable, add screenshots to help explain your problem.
Error log
With Symbols Loaded:
Additional context
This appears to be happening because the person that is entering the authentication details will always be assuming their username. To them, the username is whatever they've been using. It might be an email address, or it might literally be some sort of username.
Then, in the code, it's always assuming the email address is used. If a username was used, there will never be a user found.