Hey there,
I'm dealing with an issue with password reset flow and wondering how you handle this.
Right now, when someone clicks an expired/already-used reset link, I still show them the "enter new password" form. They don't find out it's broken until after they fill it out and click update button, which is not so good.
I can check the expire timestamp client-side to catch expired links easily. But how can I do validating the actual secret token before they waste time filling out the form?
Is there a clean way to verify the userId and secret from the reset URL when the page loads, before they even see the form? Like a validation-only endpoint or something? Or is the standard approach just to validate everything when they submit account.updateRecovery()?
Recommended threads
- function subdomain ssl certs
The generated subdomain isn't getting a valid ssl cert, I was wondering if appwrite automatically generates one or uses a wildcard for *.functions.domain.com? ...
- Searching by attribute "name" requires a...
I have a table "products" with a few columns I'm trying to search by, but I get this error: ```json { "message": "Searching by attribute \"name\" requires a...
- Issue with usage
I have a weird problem, my project on appwrite was using avarage 5-10k reads a day, it was okay, but suddenly last 7 days, reads are about 60k a day, the code h...