Service Virtualization

 View Only
  • 1.  webservice peer authentication error

    Posted Jan 14, 2016 03:33 AM

    Upon executing the web service from web service step , getting the following error. This same keystore when used in soapUI tool, its working fine. I am using LISA 7.5.1


    Failure Response:

    <?xml version="1.0" encoding="UTF-8"?>

    <soapenv:Envelope xmlns:soapenv="" xmlns:xsd="" xmlns:xsi="">




          <faultstring> peer not authenticated</faultstring>


            <ns1:stackTrace xmlns:ns1="" rel="nofollow" target="_blank">"> peer not authenticated

    at Source)

    at org.apache.http.conn.ssl.AbstractVerifier.verify(

    at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(

    at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(


    at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(

    at org.apache.http.impl.client.DefaultRequestDirector.execute(

    at org.apache.http.impl.client.AbstractHttpClient.execute(



    at org.apache.axis.strategies.InvocationStrategy.visit(

    at org.apache.axis.SimpleChain.doVisiting(

    at org.apache.axis.SimpleChain.invoke(

    at org.apache.axis.client.AxisClient.invoke(

    at org.apache.axis.client.Call.invokeEngine(

    at org.apache.axis.client.Call.invoke(




            <ns2:hostname xmlns:ns2="ATC-NA-9773</ns2:hostname" rel="nofollow" target="_blank">">ATC-NA-9773</ns2:hostname>





  • 2.  Re: webservice peer authentication error

    Posted Mar 17, 2017 08:22 AM

    Firstly, soapUI really does not care too much about the SSL connection, since it is focused on the message rather than the system, and therefore has a relatively open trust model.


    Lisa/DevTest, however, does not share this focus. That said, there are many reasons why one might receive this error, and you will need to enable some more logging at the Java level to help you identify what is going on.


    Assuming that you are running the step from the Workstation, try adding the following on a line of its own to the Workstation.vmoptions file



    This will enable some quite verbose logging at the connection level  - you will be able to find this in the workstation log file in listatmp.