Connection Error: Certification Path Failed/PKIX Path Building Failed
This error might appear if Getint isn’t able to find a valid certification path to create a connection.
Please note that this issue is outside the scope of Getint support and is not specific to Getint software. It is related to the certificates used in your connections.
Issue: Connectivity Issues between Getint (On-Premise Version) and Other Tools
Connection issues with other tools such as ServiceNow and Azure DevOps arise after replacing an expired SSL certificate. The following error message is displayed: Request failed with status code 500. PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
The problem occurs when an on-premise server uses a self-signed certificate. As a workaround, add this certificate to the list of trusted certificates in your JVM. You can either:
Edit the JAVA_HOME/jre/lib/security/cacerts file.
Run your application with the -Djavax.net.ssl.trustStore parameter.
Make sure to verify which JDK/JRE you are using, as this is often a source of confusion.
Additional Tips:
Ensure Proper Certificate Chain: Ensure that the certificate chain is complete and correctly installed on the server to avoid similar issues in the future.
Regularly Update Certificates: Schedule regular updates and replacements of SSL certificates to prevent disruptions.
Consult Documentation: Refer to your JVM’s and server's documentation for detailed instructions on managing certificates.
Atlassian also provides a guide on resolving this issue, which you can access here: Unable to Connect to SSL Services Due to PKIX Path Building Failed Error.
If you have any further questions or need assistance with other issues, feel free to contact our Support Team.
Last updated
Was this helpful?
