Briefly, this error occurs when the Java signature algorithm specified is not compatible with the SAML/XML-Sig algorithm. This could be due to a mismatch in the configuration or the absence of the required algorithm in the Java environment. To resolve this issue, you can either update the Java environment to include the required algorithm or adjust the SAML/XML-Sig configuration to use an algorithm that is available in your current Java environment. Additionally, ensure that the Java Cryptography Extension (JCE) is properly installed and configured.
This guide will help you check for common problems that cause the log ” Java signature algorithm [{}] is not available for SAML/XML-Sig algorithm [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “Java signature algorithm [{}] is not available for SAML/XML-Sig algorithm [{}]” class name is SamlAuthnRequestValidator.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
Signature sig = Signature.getInstance(javaSigAlgorithm);
sig.initVerify(credential.getEntityCertificate().getPublicKey());
sig.update(contentBytes);
return sig.verify(signatureBytes);
} catch (NoSuchAlgorithmException e) {
throw new ElasticsearchSecurityException("Java signature algorithm [{}] is not available for SAML/XML-Sig algorithm [{}]";
e; javaSigAlgorithm; queryString.sigAlg);
} catch (InvalidKeyException | SignatureException e) {
logger.warn(new ParameterizedMessage("Signature verification failed for credential [{}]";
samlFactory.describeCredentials(new HashSet<>(Collections.singletonList(credential)))); e);
return false;
