GUACAMOLE-990: Revise guacamole-auth-ban log levels to generally alwa…

…ys notify of problematic addresses.
apache · Aug 22, 2022 · fe56df7 · fe56df7
1 parent 5dea46c
commit fe56df7
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/...le-auth-ban/src/main/java/org/apache/guacamole/auth/ban/AuthenticationFailureTracker.java b/...le-auth-ban/src/main/java/org/apache/guacamole/auth/ban/AuthenticationFailureTracker.java
@@ -206,7 +206,7 @@ private void notifyAuthenticationStatus(Credentials credentials,
         AuthenticationFailureStatus status;
         if (failed) {
             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);
         }
         else
@@ -217,7 +217,7 @@ private void notifyAuthenticationStatus(Credentials credentials,
             // Explicitly block further processing of authentication/authorization
             // if too many failures have occurred
             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 "
                         + "many failed authentication attempts.",
                         "LOGIN.ERROR_TOO_MANY_ATTEMPTS");