# match anything with previous condition checking # length at least 6 characters and maximum of 20 ) # End of group Whole combination is means, 6 to 20 characters string with at least one digit, one upper case letter, one lower case letter and one special symbol (“@#$%”). Password is valid : [email protected] , true Password is valid : mk YOn12$ , true Password is valid : m [email protected] , false Password is valid : [email protected] , false Password is valid : mkyo Ng12* , false Password is valid : mkyon G$$ , false Password is valid : MKYONG12$ , false PASSED: Valid Password Test([ String;@116471f) =============================================== com.mkyong.regex.
This regular expression pattern is very useful to implement a strong and complex password.
It seems to me that when a valid set of credentials is provided, e PO commands via the API will provide positive feedback, such as an "OK:" message followed by other output; however, if the credentials are invalid, no output is produced.
I don't want to assume that no output means that the credentials were invalid, as this could actually be caused by a number of different reasons. Is there a good way to validate credentials against e PO using the API?
Obviously, I would like to notify the user if the username and password combination they provided is invalid.
Sometimes a password validation in a form is essential.