-
Notifications
You must be signed in to change notification settings - Fork 556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prefill option is lost after reset password #933
Comments
I just opened a PR to fix this. It won't use the |
@luisrudge Thank you! That makes perfect sense. Looking forward to try it out soon. |
This will be in the next release on Monday, if everything goes according to plan. 🎉 |
@larsthorup Did this fix work for you? I'm seeing that the prefill option is only filling in the forgot password email and not the login email for version 10.16.0. |
@nlake44 I am not actively using this feature at the moment, so I don't know. |
@nlake44 this is working. PLease open another issue with a repro project if it's not working for you. |
@luisrudge The prefill option does what you're showing there. But from my understanding this issue was to prefill the email field upon sign in after redirect from the forgot password flow. |
@nlake44 it also does that: |
@luisrudge Thanks for the quick response. I meant coming from the email redirect after the user has changed their password. |
Ah, right. Yeah, that is not supported 😭 |
Any suggestions on how to make it happen? |
Maybe if you edit your email template and add some info (probably the email) in the redirect link, then in your page you can check if the link exists in the url, if it exists, you add it to the prefill option. It's a long shot, but might work |
The prefill option does not carry through the reset password flow, so after requesting a password reset, Auth0 redirects back to the login screen but now with an empty email field. I would expect email to still be filled out, to minimize the chance of typos in the email field during login (which is why we are using prefill in the first place). See the screen shots below for details.
The issue can be reproduced with the HTML code below. Note that the clientId / domain combination that I use is configured for "Username-Password-Authentication" connection.
Browser: Seen in Chrome
OS: Seen on Windows
The text was updated successfully, but these errors were encountered: