![]() This concerned me because of the hassle of a user with a typo in their password, but also because in theory one could use that to guess or possibly otherwise get valid usernames. This behavior is different than providing a bad username, or providing a valid/invalid username/password combo that isn't mapped. Turns out, at least for us, if you have users mapped via ldap and you supply a valid mapped username but a bad password, sonicwall wont fail authentication, it just hangs. To make a very long story short, he was using a bad password. So I had a user constantly complaining that netextender was hanging and wouldn't let him in.
0 Comments
Leave a Reply. |