Prevent the username field from being rendered when running the identity-first login flow #43616
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.
Closes #43091
AbstractUsernameFormAuthenticator#USERNAME_HIDDENshould be set by authenticators that are executed before the username and password form to make sure their intent is respected when hiding the username field.LoginFormsProvider.USERNAME_HIDDENtotrue.LoginFormsProvider.USERNAME_HIDDENto use this new session note. However, it will require changes not strictly related to the original issue. IMO, we should also enforce a behavior different than what we have today, where once a username is provided, we always show theattempted-usernamefield so that users can restart the flow if they want. I think it is a better UX and I can create an issue for it, if you think it makes sense.