You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, users can flood the database by repeatedly signing up with the same email address, causing unnecessary database entries and potential abuse.
There is a need for a mechanism to check if a token for the same email already exists before generating a new one.
Also, implementing a TTL (Time to Live) for tokens would ensure that unused tokens are cleaned up after a specified period.
Backend:
Reuse the remove_existing_token_for_email function to check for and handle existing tokens before issuing a new one.
Implement a TTL for the token in the database to ensure that tokens automatically expire after a set time (e.g., 15-30 minutes).
Frontend:
Add a loading spinner on the signup button to indicate that the signup request is being processed.
Disable the signup button after the request is made to prevent multiple submissions.
"Here's how it looks after implementing the remove_existing_token_for_email function."
Screencast.from.2024-10-11.01-20-04.webm
The text was updated successfully, but these errors were encountered:
Description:
Currently, users can flood the database by repeatedly
signing up
with the sameemail
address, causing unnecessary database entries and potential abuse.There is a need for a mechanism to check if a token for the same email already exists before generating a new one.
Also, implementing a TTL (Time to Live) for tokens would ensure that unused tokens are cleaned up after a specified period.
Backend:
remove_existing_token_for_email
function to check for and handle existing tokens before issuing a new one.Frontend:
"Here's how it looks after implementing the remove_existing_token_for_email function."
Screencast.from.2024-10-11.01-20-04.webm
The text was updated successfully, but these errors were encountered: