Error - Trustanchors Parameter Must Be Non-Empty

Error - trustAnchors parameter must be non-empty

This bizarre message means that the trustStore you specified was:

• empty,
• not found, or
• couldn't be opened
  
  • (due to wrong/missing trustStorePassword, or
  • file access permissions, for example).

See also @AdamPlumb's answer below.

Client Authentication Tomcat - trustAnchors parameter must be non-empty

Okay - the problem was the certificate was created using JDK 1.8 and the tomcat was running with JRE 1.7 - for whatever reason this caused an issue, so the fix was to use JRE 1.8 and now everything works okay.

java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty on Linux, or why is the default truststore empty

The standard Sun JDK for linux has an absolutely ok cacerts and overall all files in the specified directory. The problem is the installation you use.

InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty on upgrading from Tomcat 7

Turns out the keystore requires a TrustedCertEntry and it only has a PrivateKeyEntry. I imported one global trusted certificate using keytool and the issue is resolved.

Error - trustAnchors parameter must be non-empty

This bizarre message means that the trustStore you specified was:

• empty,
• not found, or
• couldn't be opened
  
  • (due to wrong/missing trustStorePassword, or
  • file access permissions, for example).

See also @AdamPlumb's answer below.

javax.net.ssl.SSLException - the trustAnchors parameter must be non-empty

You haven't mentioned which JDK or OS/distro you are using, but it's possible that ca-certificates-java is not a dependency in the Oracle JDK/JRE so this must be explicitly installed.

You might need to run

sudo /var/lib/dpkg/info/ca-certificates-java.postinst configure

See also
Error - trustAnchors parameter must be non-empty

Error - trustAnchors parameter must be non-empty

This bizarre message means that the trustStore you specified was:

• empty,
• not found, or
• couldn't be opened
  
  • (due to wrong/missing trustStorePassword, or
  • file access permissions, for example).

See also @AdamPlumb's answer below.

---

Related Topics