Forum Discussion

Sachin_Sawe__Pr's avatar
Sachin_Sawe__Pr
Contributor
15 years ago

soap monitor behavior w/ soapui as client vs an external java program as client

Ole/Robert,

I observed that soapui monitor interaction changes when I issue a web service request using soapui as a client vs when issued the same request using external java app as client. Here are more details on scenario:

Using soap monitor as http tunnel when:

1. Our application sends a message X with ssl cert abcd.pfx attached to it to an external web service. If I test this behavior within soapui where I use soapui as my client and send this message X with ssl cert to external web service it works fine. That is to say that soap monitor setup as http tunnel captures messages as expected.

   soapui client => sends message X with ssl cert => soap monitor as http tunnel at localhost:8081 => ext web service

2. Now if I use our application as a client to send message X with ssl cert abcd.pfx to the same web service and try to capture messages using exact same soap monitor set up exact same way then that does not work. instead I see an error in our application log.

  java app => sends message X with ssl cert => soap monitor as http tunnel at localhost:8081 => ext web service

The error I see in application log is result of interaction between our app and soap monitor and this error is:

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

What could be going wrong here?

Thanks,
Sachin

3 Replies

  • I am using these certs on soap monitor. I am sending a cert to soap mon and using the  keystore, truststore having this cert with soap monitor. Do I also need to configure truststore and keystore for my java client?

    Sachin