[
https://issues.apache.org/jira/browse/RANGER-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511336#comment-17511336
]
kirby zhou edited comment on RANGER-3678 at 3/23/22, 4:08 PM:
--------------------------------------------------------------
It works. But in my opinion, it is meaningless to check isLetter. it is
something like Correct nonsense.
Can you construct a password case which have different vaildate result with /
without isLetter check?
In my more radical thinking, we should limit the password string to characters
in the range of 32~127. This can avoid the problem that it is difficult to
enter the password on the keyboard.
was (Author: kirbyzhou):
It works. But in my opinion, it is meaningless to check isLetter. it is
something like Correct nonsense.
Can you construct a password case which have different vaildate result with /
without isLetter check?
> Update password validation criteria
> ------------------------------------
>
> Key: RANGER-3678
> URL: https://issues.apache.org/jira/browse/RANGER-3678
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 3.0.0
> Reporter: Bhavik Patel
> Assignee: Bhavik Patel
> Priority: Major
>
> Update password validation for "passwordchange" api and changepassword
> utility.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
