Forum Discussion

Gopikakrishna's avatar
Gopikakrishna
New Contributor
15 years ago

How we can test WSHttpbinding with SoapUI tool

Hi,

I am testing application developed on WCF which is internally using WSHttpbinding. While testing the same using SoapUI , it is giving an error message. When I changed the WSHttpbinding to basicHttpbinding then it works fine. But I can't change that in Production environment for the sake of testing purpose alone.


I am gettign following error message.

The message could not be processed. This is most likely because the action 'http://service.wellsfargo.com/provider/wfa/1bcr/businessDate/2010/05/IbusinessDate201005PortType/PeformValidation' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.


Please let me know how to test the application without changing from WSHttpbinding to basicHttpbinding in the code.


Thanks,

Hari.
  • raghumvs's avatar
    raghumvs
    New Contributor
    15 years ago
    Hi, how did you change your wshttpbinding to basichttpbinding. Sorry for asking a question to your question.

    Thank you

    Gopikakrishna wrote:

    Hi,

    I am testing application developed on WCF which is internally using WSHttpbinding. While testing the same using SoapUI , it is giving an error message. When I changed the WSHttpbinding to basicHttpbinding then it works fine. But I can't change that in Production environment for the sake of testing purpose alone.


    I am gettign following error message.

    The message could not be processed. This is most likely because the action 'http://service.wellsfargo.com/provider/wfa/1bcr/businessDate/2010/05/IbusinessDate201005PortType/PeformValidation' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.


    Please let me know how to test the application without changing from WSHttpbinding to basicHttpbinding in the code.


    Thanks,

    Hari.


  • ajayakumar_bme's avatar
    ajayakumar_bme
    15 years ago
    Change web.config by adding the following:

    <bindings>
    <wsHttpBinding>
    <binding name="wsHttpBindingNoSCT">
    <security mode="None">
    <transport clientCredentialType="None" />
    <message establishSecurityContext="false" />
    </security>
    </binding>
    </wsHttpBinding>
    </bindings>


    Reset the iis once & test the service with Wshttp binding in SOAPUI....Its will work...
    • tansonly's avatar
      tansonly
      New Contributor
      8 years ago

      Hi ,

       

      Can you please advise where I can find web.config file to update?

       

      I am having similar issue .