Forum Discussion

Sachin_Sawe__Pr's avatar
Sachin_Sawe__Pr
Contributor
15 years ago

Capturing traffic between local webservice and external ssl based webservice

Hi Robert,

Consider a case where I am issuing a HTTP request to my webservice running on localhost:8080. This webservice then in turn sends HTTPS request to an external webservice. I want to monitor traffic between our localhost:8080 and external webservice. I am trying to do this by setting up soapui monitor as a proxy running at localhost:8081. My local webservice is configured to send request to endpoint, say, https://www.abcd.com/soap/externalService using security certificate. My local service also uses concept of a proxy server and that is where I register localhost:8081 as a proxy server. I have setup soapui monitor at localhost:8081 using Http proxy method (not the tunnel method). When I set up this monitor I also gave it an incoming-ws config where I specify by signature certificate that is required by external web service.

Here is the problem:
When I issue the request to my local web service at localhost:8080, my webservice internally sends request to the proxy at localhost:8081. But then I receive a response back from localhost:8081 saying:

- I/O error: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?; nested exception is javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
org.springframework.ws.client.WebServiceIOException: I/O error: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?; nested exception is javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?

I feel that proxy is having a plain socket and not able to send ssl message coming from my local web service on plain http proxy connection.

I also tried using http tunnel for this purpose where tunnel listens on localhost:8081 and my webservice is still configured to use localhost:8081 as proxy. In that case I get "connection refused error".

Any thoughts in getting this running?

Thanks in advance,

Sachin

11 Replies

Sort By
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    15 years ago
    Hello,

    Well, yes proxy only handle plain http. Tunnel is one that can handle ssl. Idea is to make a tunnel be able to decode ssl and make it visible, which can not be done with proxy. Usage is also different, while to use proxy you need to set global preference proxy ( host, port, etc ), for tunnel you set port, end point and certificate in case you are using ssl( this is not necessary in case of plan http) and send request to tunnel not web service server. Tunnel will send request to ws server and get back to client( soapUI ).
    So, to set up tunnel, set port ( ex. 8081 ), endpoint ( https://www.abcd.com/soap/externalService ) and certificates. Than send request to https://localhost:8081. That should be it..

    Let me know does it helps,
    robert
  • Sachin_Sawe__Pr's avatar
    Sachin_Sawe__Pr
    Contributor
    15 years ago
    Hi Robert,

    I tried this option. My request goes to my local webservice at http://localhost:8080. Then I can see in the logs that it is issuing request to external web service at http://www.abcd.com/soap/externalWebService with the message that is supposed to be sent to this service. At this point in time I get error

    I/O error: Connection refused; nested exception is java.net.ConnectException: Connection refused
    org.springframework.ws.client.WebServiceIOException: I/O error: Connection refused; nested exception is java.net.ConnectException: Connection refused

    It appears that when issue request from my local webservice to an http tunnel monitor in soapui the monitor is not aware of how to handle it. However if I try the same thing (that is issuing of request to external web service) manually inside soapui where I issue soapui request with message to external web service and create soap monitor tunnel to external web service then that works as expected.

    Any ideas why?

    thanks,
    Sachin
  • Sachin_Sawe__Pr's avatar
    Sachin_Sawe__Pr
    Contributor
    15 years ago
    The error I typed is the error in my localhost tomcat log. But no error in soapui log. The error I get back in soapui is internal server error that is reported by my local host tomcat service.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    15 years ago
    Hello,

    Did you setup tunnel properly? How did you set tunnel port and endpoint? And what is local ws endpoint?

    robert
  • Sachin_Sawe__Pr's avatar
    Sachin_Sawe__Pr
    Contributor
    15 years ago
    Robert,

    See here is what I feel but you can correct me if I am wrong. soap ui suggests that user point to localhost:8081 when 8081 tunnel is running as soapui monitor. This can perhaps work if you point to localhost:8081 and keeping rest of url for webservice same only if you do this from within soapui. I have tried this from one soapui to another soapui instance and that works too.

    In this case what I doing is invoking tomcat localhost call to an ip:port/monitorServiceInSoapUI. Do you think this would work? Essentially can we invoke a call to soapui monitor running as tunnel and that call is invoked from external tomcat?

    Attached is the snapshot of my tunnel setup.

    Thanks,
    Sachin
  • Sachin_Sawe__Pr's avatar
    Sachin_Sawe__Pr
    Contributor
    15 years ago
    Robert,

    I just tried my exercise directly in soapui but soapui http tunnel monitor is not listening on localhost:8081. Is it possible that the bug you fixed earlier in order to get "tunnel > global proxy > external web service" could have created another bug? I ask this because I am using your nightly build as of october 9th. The one you suggested after you got "tunnel > global  proxy > external service" thing working. And I do remember before I tried this build that my soapui tunnel monitor was working

    Please let me know

    Sachin
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    15 years ago
    Hello,

    Hm..I just tried it and it works for me..One more question do have setup proxy? If you set up external proxy soapUI is trying to send request over it to your local tomcat...If this is case remove it or add server to exclude...

    Let me know,
    robert
  • Sachin_Sawe__Pr's avatar
    Sachin_Sawe__Pr
    Contributor
    15 years ago
    No. I don't have proxy set up. What did you try? Did you try connection to external web service via http tunnel soap monitor and invoke this connection using a local webservice using local web server?

    thanks,
    Sachin
  • Sachin_Sawe__Pr's avatar
    Sachin_Sawe__Pr
    Contributor
    15 years ago
    Robert,

    I figured this one out. Basically there is a bug underlying soapui monitor with http tunnel functionality. This bug is such that if there is anything wrong with http keystore or truststore then it throws error on console but does not actually start the monitor. It however shows you the monitor in UI so user feels monitor has started but actually it has not. That is why I was getting Connection refused because the monitor was not at all running on port 8081. Please note this bug for future references so you guys can fix it.

    I do have another follow up questions as I progressed further on this. But I shall create a separate topic for that

    Thanks,
    Sachin