Forum Discussion

Shirate's avatar
New Contributor
6 years ago


Hi ,

when I try to execute a request in Soap Ui,

when my webConfig is configured as the follwoing:


<service behaviorConfiguration="BillingHost.GeneralServiceBehavior" name="Ness.Wcf.Billing.CustomerService">
<endpoint address="" behaviorConfiguration="InspectionBehavior" binding="wsHttpBinding" bindingConfiguration="wsHttpSecurityMessage" contract="Ness.Wcf.Billing.ICustomerService">
<dns value="localhost" />
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />



<binding name="wsHttpSecurityMessage">
<security mode="Message">
<transport clientCredentialType="Windows"
proxyCredentialType="None" realm="" />
<message clientCredentialType="Windows" negotiateServiceCredential="true"
algorithmSuite="Default" establishSecurityContext="true" />



it fails on "The message could not be processed. This is most likely because the action '' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bi......."


when I change it to security mode="None"

it works!

How can I make it to work when security mode="message"????

Thanks  a lot


4 Replies

    • Shirate's avatar
      New Contributor

      I'll check it!

      Thanks a lot!!

    • Shirate's avatar
      New Contributor


      I understood from your a post that you refered me to look at, that SoapUI will work with wsHttpBinding with Transport security.

      Can you please provide me an example for that?


      Another thing, I was trying to do the same as it was posted with the

      <behavior name="NoTrust">
      <authentication certificateValidationMode="None"/>


      And it still didn't work...

      So for the meantime nothing is working except mode="none"

      I would really appricate if you can please provide me examples for bothe cases!


      Thanks a lot!!!


      • Nastya_Khovrina's avatar
        SmartBear Alumni (Retired)

        Hi Shira,


        Unfortunately, we don't have any examples for wsHttpBinding. The article states that the wsHttpBinding binding most likely isn't supported in ReadyAPI since it requires some protocols, which are not supported.


        As a workaround, you can switch to the BasicHttpBinding binding.