Fix the condition for logging empty JWK sets. (#91675) (#91678)

The logic for check isEmpty should have been flipped. This PR fixes it. Relates: #91001
elastic · Nov 18, 2022 · e7011ef · e7011ef
1 parent 57c80fa
commit e7011ef
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/...urity/src/main/java/org/elasticsearch/xpack/security/authc/jwt/JwtSignatureValidator.java b/...urity/src/main/java/org/elasticsearch/xpack/security/authc/jwt/JwtSignatureValidator.java
@@ -161,8 +161,10 @@ public void close() {
         }
 
         private void logWarnIfAuthenticationWillAlwaysFail() {
-            final boolean hasUsableJwksAndAlgorithms = (hmacJwtSignatureValidator != null && hmacJwtSignatureValidator.jwksAlgs.isEmpty())
-                || (pkcJwtSignatureValidator != null && pkcJwtSignatureValidator.jwkSetLoader.getContentAndJwksAlgs().jwksAlgs().isEmpty());
+            final boolean hasUsableJwksAndAlgorithms = (hmacJwtSignatureValidator != null
+                && false == hmacJwtSignatureValidator.jwksAlgs.isEmpty())
+                || (pkcJwtSignatureValidator != null
+                    && false == pkcJwtSignatureValidator.jwkSetLoader.getContentAndJwksAlgs().jwksAlgs().isEmpty());
             if (false == hasUsableJwksAndAlgorithms) {
                 logger.warn(
                     "No available JWK and algorithm for HMAC or PKC. JWT realm authentication expected to fail until this is fixed."