Studio Debug Fails With Unable to Find Valid Certification Path While the Deployed Integration Succeeds
What does "Root Cause: sun.security.provider.certpath.SunCertPathBuilderException" mean in Workday Studio?
The outbound HTTPS call fails only when the integration is debugged from Studio on your own machine. The local Java installation does not trust the certificate the remote server presents, while the Workday cloud runtime does.
Quick fix
Import the missing CA or intermediate certificate into the truststore of the JVM that Studio runs on, then restart Studio and debug again.
Permanent fix
Keep the local debug environment's truststore aligned with the certificate authorities your integrations actually call, and refresh it whenever an endpoint rotates its certificate or changes CA. Where the failure comes from a corporate TLS-inspecting proxy, add that proxy's CA to the debug truststore as part of standard developer setup. Do not disable certificate verification to work around it: the cloud runtime is validating correctly, and only the local environment is short a trust anchor.
Troubleshooting
- Establish where it fails. If the integration completes when launched from the Workday UI and only fails under Studio debug, this is a local trust problem, not an integration defect.
- Identify the exact endpoint the HTTP call targets at the point of failure, including host and port.
- Retrieve the certificate chain that host presents and check which authority signed it. An internal or private CA is the usual cause, and so is a server that sends only its leaf certificate while omitting the intermediate.
- Check which Java runtime Studio is using, then locate the truststore that runtime actually reads.
- Confirm whether that truststore already holds the signing CA. If it does not, the local JVM cannot build a path to a trusted root and throws this before any request leaves the machine.
- Rule out a proxy performing TLS inspection on your network, which replaces the server certificate with one signed by a corporate CA the JVM has never seen.