soapUI is back, with lot more for you.

It has been a long time since I last used soapUI - see my 2007 post - when I was using version 2.1.x. Today, I got 4.5.1, from the same location: http://www.soapui.org/

I wanted to test a simple WS using WS-Security username token and ran into an interesting issue; the invocations were failing with an HTTP error : 401 Unauthorized. 

The solution was simple - switch the HTTP authentication to use preemptive mode (see documentation).

Changes to Request Setup

Here are 2 common HTTP errors codes:

HTTP/1.1 403 Forbidden	The username/password you provided is not valid.
HTTP/1.1 401 Unauthorized	The server is sending back an auth challenge that may be ignored by the HTTP client library - the hint on the response is "WWW-Authenticate: BASIC realm="owsm".

And 1 common soap fault:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  <env:Header/>
  <env:Body>
    <env:Fault xmlns:ns0="http://schemas.oracle.com/owsm/policy-enforcement-2007-06">
      <faultcode>ns0:GenericFault</faultcode>
      <faultstring>GenericFault : generic error</faultstring>
      <faultactor></faultactor>
    </env:Fault>
  </env:Body>
</env:Envelope>

The key here is ns0 - the GenericFault is related to policy enforcement. This is the only hint you will get from the server. For the reason of the failure, you will have to look on the server side logs. For some obvious security reason, the true root cause is not provided to limit potential exploits.

Regarding WS-Security setup, it's all here in the soapUI documentation.

More on this to come in some follow-up post.