Question


Anthem
US
Last activity: 5 Sep 2019 18:48 EDT
Soap Integration with Security issue.
Hi All,
I'm trying to integrate to an HTTPS secure wsdl. I'm receiving below linked issue.
** Security Exception. Check digital certificate. Enable SSL debugging for more details..
** Security exception. Unable to verify an authenticated connection; check digital certificate.
Things we know about the integration. The certificate is stored on the JVM and configured properly. The current endpoint we are using is in use in production as is sending requests and receiving responses.
What they have asked us to do is regenerate the wsdl. When I try to integrate using the The connector integration wizard this is the message that comes up.
Do I absolutely need to have a Keystore rule on the pega side or is having the certificate in truststore.xml ok?
This wsdl is avaible in a browser but not reachable from Pega side.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!


Pegasystems Inc.
US
what is your app server (guess WAS?) and Pega version? Did you specify truststore in the connect-soap rule form? (that takes the precedence over JVM/app server level truststores). The wizard code flow is different from that of connect-soap runtime - which may explains why it works for connect-soap. Please attach the full pega rules logs if possible.


Anthem
US
Hi Kevin thanks for the response.
We have a tomcat appserver setup and pega version is 7.1.8.
We did not have a trust store specified in the connect soap rule at all.
I've looked through the logs and there is nothing more than the error message shown in the screen cap attached. I can access that endpoint in the browser which is very strange.


Anthem
US
Hi Kevin,
Here is a snippet of the log when integrating.
Hi Kevin,
Here is a snippet of the log when integrating.


Pegasystems Inc.
US
You can refer to this link: https://collaborate.pega.com/question/configuring-two-way-ssl-pega-74-apache-tomcat. For you, you only need to configure truststore if it is just one way SSL to the endpoint. You said it was already done at JVM level, can you share the current JVM arguments? It should work either way (server.xml or JVM).


Anthem
US
We dont have direct access to the server nor the configurations of the environments. Another team handles it. I will have to get back to tommorow for the JVM arguments or the server.xml file. I will let you know in the morning. Thanks alot for the help.