Skip to content
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

Password rule for WAS Admin user (wsadmin) should allow more special chars #29

Open
git4rk opened this issue May 26, 2021 · 2 comments
Open

Comments

@git4rk
Copy link
Contributor

git4rk commented May 26, 2021

  • When I used a password with special chars like $ ! _ / the deploy/login failed
  • Rule was updated in CreateUIDefinition.json to restrict special chars:
    • Password must be at least 12 characters long and not contain any of the following characters: !#$&*/?^
  • We need to allow most of these special chars
@majguo
Copy link
Collaborator

majguo commented May 26, 2021

@git4rk @edburns
As we just agreed in the Slack channel, let's use the same regex used in WebLogic administrator password:

{
                        "name": "wlsPassword",
                        "type": "Microsoft.Common.PasswordBox",
                        "label": {
                            "password": "Password for WebLogic Administrator",
                            "confirmPassword": "Confirm password"
                        },
                        "toolTip": "Password for WebLogic Administrator",
                        "constraints": {
                            "required": true,
                            "regex": "^(?=.*[A-Z])(?=.*[a-z])(?=.*\\d)[A-Za-z\\d]{12,}$",
                            "validationMessage": "The password must contain at least 12 characters, with at least 1 uppercase letter, 1 lowercase letter and 1 number, and special characters are not allowed."
                        },
                        "options": {
                            "hideConfirmation": false
                        },
                        "visible": true
                    }

As you can see, special characters are not allowed. So let's follow the same pattern to quickly fix the issue.

@edburns
Copy link
Collaborator

edburns commented May 26, 2021

The plan of record is to fix it using the simple regex shown by @majguo in this comment but resolve it after MVP release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants