You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, a comma is a wrong character, that when unescaped, throws an exception during search. Comma could be there, because you can have a group name:
HSBC (Pvt.) Ltd., Asia
(^ the character needing escaping is a comma, which will get escaped by LDAP. NEEDS TESTING!!)
Backend tests:
Groupname with a backslash
Groupname with a comma
Groupname with backslash, that is member of a group of the user
Groupname with comma, that is member of a group of the user
"Frontend" tests - supply values to authenticator:
Comma in a username
Dot in a username
Backslash in a username
The text was updated successfully, but these errors were encountered:
As in #2 , the values coming either from user and/or LDAP itself, can contain unescaped sequences.
Escape values properly, ie. using this -> http://php.net/manual/en/function.ldap-escape.php
For example, a comma is a wrong character, that when unescaped, throws an exception during search. Comma could be there, because you can have a group name:
HSBC (Pvt.) Ltd., Asia
(^ the character needing escaping is a comma, which will get escaped by LDAP. NEEDS TESTING!!)
Backend tests:
"Frontend" tests - supply values to authenticator:
The text was updated successfully, but these errors were encountered: