GUACAMOLE-990: Revise guacamole-auth-ban log levels to generally always notify of problematic addresses.

This commit is contained in:
Michael Jumper
2022-08-22 12:19:52 -07:00
parent 8b981d9213
commit a9ed4c2982

View File

@@ -206,7 +206,7 @@ public class AuthenticationFailureTracker {
AuthenticationFailureStatus status; AuthenticationFailureStatus status;
if (failed) { if (failed) {
status = getAuthenticationFailure(address); status = getAuthenticationFailure(address);
logger.debug("Authentication has failed for address \"{}\" (current total failures: {}/{}).", logger.info("Authentication has failed for address \"{}\" (current total failures: {}/{}).",
address, status.getFailures(), maxAttempts); address, status.getFailures(), maxAttempts);
} }
else else
@@ -217,7 +217,7 @@ public class AuthenticationFailureTracker {
// Explicitly block further processing of authentication/authorization // Explicitly block further processing of authentication/authorization
// if too many failures have occurred // if too many failures have occurred
if (status.isBlocked()) { if (status.isBlocked()) {
logger.debug("Blocking authentication attempt from address \"{}\" due to number of authentication failures.", address); logger.warn("Blocking authentication attempt from address \"{}\" due to number of authentication failures.", address);
throw new TranslatableGuacamoleClientTooManyException("Too " throw new TranslatableGuacamoleClientTooManyException("Too "
+ "many failed authentication attempts.", + "many failed authentication attempts.",
"LOGIN.ERROR_TOO_MANY_ATTEMPTS"); "LOGIN.ERROR_TOO_MANY_ATTEMPTS");