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
I'm using this package for 2 weeks with SMS channel. I noticed that users are spamming by only refreshing otp protected routes.
I could prevent this by extending middleware and putting a simple condition with otp_last_sent timestamp in session and a simple timer in otp.create view to show that they can only request for new code after 1 minute.
I think you can implement this with dynamic time in config file in future releases.
The text was updated successfully, but these errors were encountered:
mssayari
changed the title
prevent user to spam otp
prevent users to spam otp
Dec 6, 2021
Hi,
I'm using this package for 2 weeks with SMS channel. I noticed that users are spamming by only refreshing otp protected routes.
I could prevent this by extending middleware and putting a simple condition with otp_last_sent timestamp in session and a simple timer in otp.create view to show that they can only request for new code after 1 minute.
I think you can implement this with dynamic time in config file in future releases.
The text was updated successfully, but these errors were encountered: