Forum Discussion

lena92's avatar
New Contributor
8 months ago

SOAP Tests aren't running after updating ReadyAPI

Hey guys,

After updating from ReadyAPI 3.43 to 3.49 my SOAP tests no longer work.

I was able to narrow down the problem to the outgoing WSS.
It looks as if the Basic(Bultin) authentication method requires an outgoing WSS, otherwise ws-security policies do not work.
After adding outgoing WSS the tests are working. Attached is the error message:

HTTP/1.1 500 500
Date: Thu, 30 Nov 2023 14:05:02 GMT
Server: Apache
Strict-Transport-Security: max-age=31536000
Content-Type: text/xml;charset=UTF-8
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin
Connection: close
Transfer-Encoding: chunked

<soap:Envelope xmlns:soap=""><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>These policy alternatives can not be satisfied:

Why is it required to add an WSS in this version, when it wasn't necessary in version 3.43? Is there a way to circumvent this WSS requirement?

3 Replies

  • richie's avatar
    Community Hero
    Hey lena92

    It's quite likely this was a regression introduced between the version you were previously using and the latest you installed.

    Several people have posted on the forum recently saying they've upgraded and the upgrade has broken their tests.

    There's no real advice o can think of to recommend. Typically i'd advise to NOT update to the latest version straight away (as soon as the version is available) but to wait to determine if the latest version is stable. (I myself sit about 5 or 6 releases behind the latest version for just this reason). However you had a version from a while ago, so upgrading was a reasonable thing to do in your case.

    SmartBear are likely unaware this issue has been introduced (and i can't imagine why it would be intentional), so it would help SmartBear (and us, it's customers) if you raised a support ticket outlining the issue you found.

    You can raise a support ticket via here -->


  • lena92 richie 

    This is fixed in the next version 3.5 which comes out in a week. It was introduced in the build after 3.44.1 (which I have been stuck on for many months now).