Last activity: 6 Nov 2015 12:35 EST
Issue with Connect Soap
In our Application we have a Web service and the Source system migrated their service from V1 to V2 and hence we are moving from V1 to V2. After Consuming the V2 WSDL we are getting the below issue while using the Test Connectivity in Connect-Soap Rule
"<Service End Point URL>" value is invalid: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target
Source System did not migrate to new Servers and i think we dont need any Certificates need to install as it is the same servers ? Any Ideas?
is V2 on the same port or different port as V1? Does the same use case work for V1?
I suspect your old end point worked as it might be http. Your new endpoint might be updated manually after you guys ran the wizard with https. Is the endpoint hard-coded or its using global resource settings? Since you stated that there are no changes at environment level, I don't think this error is related to ssl certificates related.
Is your SOAP service SSL secured? What version of Pega are you using?
Yes it is SSL Secured. PEGA 7.1.5
May be once you moved from V1 to V2 webservice, V2 required different set of certs which may not be present in your JKS truststore file or your JVM's jdk cacert?
Yep. I checked with Service Provider if we need to install another set of Certs. They confirmed its not required . Only Option at this Point is to reinstall the same certs and check. Will Check and will Post the results .
I am confident that there is a cert missing. You can also add SSL DEBUG argument to your JVM, this will give us more verbose information during SSL handshake (You would have to restart your app server after this).
Other App server:
Deleted the Certificate and Installed once again and this Fixed this issue
Thanks all for your help.
Both V1 and V2 are in HTTPS . we are using Global Resource Settings for both V1 and V2
V1 and V2 are in the same Port. V1 is working fine even now