Self Registration Secondary Userstore username Regex Validation #21639
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Describe the issue:
For secondary user store users, username length is considered with secondary user store domain name while validating the entered username in <IS_Home>/repository/deployment/server/webapps/accountrecoveryendpoint/self-registration-username-request.jsp. Hence if actual entered username character length is lesser than the defined pattern, but if it matches the regex when considered with the domain name the username is allowed and user will redirect to collect required information for account creation.
However after submitting the user data, user will experience a blank page as username validation fails while creating the user. Hence user creation also get failed.
How to reproduce:
Create a Secondary userstore with domain name 'SECONDARY'
Enable self-user registration
For the secondary user store define following regex for the user name to expect username length 8 - 20 characters
Username RegEx (Java) - [a-zA-Z0-9._-|//]{8,20}$
Username RegEx (Javascript) - ^[\S]{8,20}$
Go to my account and choose create account option
In interface to enter user name enter username with user store domain name - SECONDARY/din
since it has characters more than 8, entered username will be allowed and user will be redirected to enter details for user creation
After submitting the data user will end up in a blank page
If DEBUG logs enabled following error stack trace can be observed as username din does not pass the username regex validation.
Expected behavior:
Entered username should be validated with the username regex without considering the user store domain and prevent user proceed with the next steps and show the Username RegEx Violation Error Message
Environment information (Please complete the following information; remove any unnecessary fields) :
Optional Fields
Related issues:
Suggested labels:
The text was updated successfully, but these errors were encountered: