Hello Mark,
it’s case insensitive. Strings are converted to lowercase before they are compared.
Thanks for the reply. I just wish to understand what you said, when you said the strings are converted to lowercase before they are compared.
How does that translate to a user name shown as “ADMIN” versus ‘admin’?
If the string “ADMIN” is converted to lower case of “admin” and compared to ‘admin’, are they not the same and one cancels out?
Hello again Mark,
when both strings that are to be compared are converted to lowercase it will result in a match on the blocking pattern. So if you add “admin” it will block anyone trying to log in with “admin”, “ADMIN” or “aDmiN”.
Ah, that is much clearer.
Ok, so to add in “ADMIN” and ‘admin’ is not required, all I need to do is just add the string in lower case and it will cover all variations including case sensitive variations of the same string.
Got it. 🙂
I see that I should be more precise in my question which was my fault. I should have asked “Do I need to add case sensitive versions of the same word to cover case sensitive variations”.
Thanks for the help.
It’s alright Mark glad we were able to sort it. 🙂
