An option to hide username in signup view #1954
Merged
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.
Added an option named signUpHideUsernameField to hide username in signup view for the connections that have user name enabled.
Changes
This is the second time I came across this request. Customers have custom DBs and some of the users use the username to log in. Going forward the customers want to enable signup only with an email so they want to hide the username option from the signup view. Customers can't simply disable the user name option from the connections setting due to the legacy users using a username.
The solution hides the signup field with a feature option which is by default turned off. Once the option is enabled it helps to hide the username from Signup.
The solution is coded such that once the feature is enabled a random username is created with the allowed max length and passed to signup API. That is needed because, for the connections that have the username option turned on, passing the username is obligatory.
I will open a request to the doc team when the PR is merged.
References
https://support.auth0.com/tickets/00473546
Testing
Please describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
Checklist