| Attempting to login with any user/password other than admin/geoserver results in brute force attack prevention measures being activated, even with perfectly valid logins. I can clearly see (in a debugger) that the class BruteForceListener is always invoked twice – once for the actual user login sent from the login form, and then the second time with "admin/geoserver" credentials. I think this is because the home page is trying to check whether the default admin password has been changed in order to display a warning. Anyway, this results in log messages claiming there was a failed login attempt, as well as a few second delay being triggered. I tested this in 2.10.4 and 2.13.1, it looks like this bug has been around for a while. How to reproduce
- Start geoserver on top of the default data directory included with binary distributions
- Login as admin
- Change admin password; the change is accepted, but server log output contains this:
Note the "Failed login... / Brute force attack prevention ..." lines
- Log out and log in with the new password
- Credentials are accepted accepted, but response is delayed and this appears in server output:
|