Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Not able to consume XSD

SA-31164

Summary



User is unable to consume XSD.

Displays an error "Couldn't resolve URL https://hostname:10701/xsd/file.xsd " while loading the schema using document URL option.

Verified the certificates and no issues found.



Error Messages


[11/30/16 16:13:53:198 CST] 000000a0 SystemOut     O WebContainer : 6, handling exception: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.n: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: 
     java.security.cert.CertPathValidatorException: The certificate issued by CN=Common Name, OU=Certification Authorities, O="Organization name", C=US is not trusted; internal cause is: 
     java.security.cert.CertPathValidatorException: Certificate chaining error 

 

Steps to Reproduce



1. Start the Connector and Metadata Wizard. Choose the option to consume an XSD.
2. Choose option "Document URL" and provide the URL of the XSD.


Root Cause



A defect or configuration issue in the operating environment. 
Signer certificate from the external server was not present in the default IBM Java trustStore (cacerts).

Resolution



Make the following change to the operating environment:

User explicitly specified IBM Websphere JVM to use already setup using generic VM argument "-Djavax.net.ssl.trustStore={Websphere_HOME}/appserver/profiles/.../truststore.p12".
Suggest Edit

Published December 21, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us