Expose email on reset-password-email screen data#329
Merged
amitsingh05667 merged 1 commit intoauth0:masterfrom Mar 9, 2026
Merged
Conversation
nandan-bhat
approved these changes
Mar 6, 2026
amitsingh05667
approved these changes
Mar 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR exposes the email field on the reset-password-email screen so it is accessible to frontend consumers via
useScreen().data.email.After submitting an email on the reset-password-request screen, the server correctly returns the submitted email address in the screenContext.data for the subsequent reset-password-email screen. However, this value was not accessible from the frontend SDK because:
In practice, username is often unset for this screen, while email contains the relevant value needed to render confirmation UI (e.g. “We sent an email to…”).
Changes
This brings the frontend SDK in line with the data already provided by the server and matches developer expectations.
Impact
References
Related issue:
Testing
Environment
@auth0/auth0-acul-react: 1.0.0
Browser: Chrome
Checklist