javax.net.ssl.SSLHandshakeException: PKIX path building failed when QTest REST API uses self‑signed certificate

Problem Overview

When QTest tries to call its REST endpoint over HTTPS using a self‑signed or otherwise untrusted certificate, the Java HTTP client throws a javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed error. This prevents the integration from authenticating and makes the API unusable.

DNS Resolution Failure

Similarly, if the hostname cannot be resolved, QTest logs a generic Failed to resolve host: <hostname> exception from Apache HttpClient. The error is buried in the client stack and often appears as a silent failure.

Configuration Constraints

QTest’s REST client hard‑codes the SSL context to the default JVM truststore and does not expose any option to supply a custom truststore or disable certificate validation. The only workaround is to modify the global JVM truststore or proxy the API through a trusted gateway.

Unresolved Decision

It remains unclear whether QTest will ever provide a configuration hook for a custom truststore or allow SSL verification to be turned off. This limitation forces users to balance security with operational feasibility.

Specific Questions

• What options exist to supply a custom truststore to QTest’s REST client without altering the global JVM truststore?
• Can the SSL context be overridden programmatically or via configuration within QTest?
• What security implications arise from disabling certificate validation in QTest?