prevent accidental lockout from restricted chars in single pass mode #1352
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.
Pull Request Type
Relevant Issues
resolves #1289
What is in this change?
Prevent a password-protected instance from being self-owned by accidentally using
.envfile-protected chars in their password since they will be either removed or escaped and therefore the password will no longer match or will be broken on instance reboot as loading from the.envon boot will only boot what the system can read as opposed to what the user actually wanted the password to be.Regex:
/^[a-zA-Z0-9_\-!@$%^&*();]+$/Additional Information
Developer Validations
yarn lintfrom the root of the repo & committed changes