Forum Discussion

SuperG's avatar
SuperG
New Contributor
11 years ago

Authentication / SoupUI

I am very new with web services or at least WCF web services. I have been successfully using SOAPUI to test our WCF web service until I had the requirement to enable BASIC security on the service. W...
GiscardN's avatar
GiscardN
Frequent Contributor
11 years ago
Hi,

WCF web services turn on wsHttpBinding by default. wsHttpBinding turns on a number of WS-* protocols by defaults. Some of them we support, such as:
WS-Security, WS-Addressing and WS-ReliableMessaging.
But there are other standards used in wsHttpBinding that are not supported by SoapUI Pro (e.g. WS-SecureConversation, WS-SecurityPolicy).
Our clients that test WCF web services would usually change to BasicHttpBinding. Then you can configure SoapUI Pro as described in the following article: http://www.robert-nemet.com/2011/10/soa ... t-one.html

Regards,

Giscard
SmartBear Support
  • marko's avatar
    marko
    New Contributor
    8 years ago

    Hi 

    We are using certificate validation as security measure for web service that we have built
    Now we are facing technical problem that is preventing us from using SoapUI anymore. 
    There is no way to force SoapUI to use certificates to validate access to our web service call. 
    We were testing this web service and certificate authentication is working when we run it from our code or other tools like WCF test client.
    Our service is using standard WCF wsHttpBinding and we found some blog posts on the web that soap UI cannot work with that kind of binding.
    Is this true ? If this is true, than we have to stop using your product. 
     
    We have followed this procedure with no success : 
     
    we have tried even older versions, and it is not helping at all : 
     
     
    The same message that we are getting again and again : 
     
    <s:Text xml:lang="en-US">The message could not be processed. This is most likely because the action 'http://tempuri.org/IService/GetTypes' 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.</s:Text>
     
     
    Can you please advise if you have any solution for this issue. 
    Thanks, 
    Marko