Contributions
Trying to get SoapUI work against WCF wsHttpBinding
I saw a post from a few years ago that said SoapUI won't work with wsHttpBinding unless we remove security elements, but we noticed that it will work when we use Transport security... We have a self hosted service that uses wsHttpBinding but can be configured for either Transport or Message security. When configured for Transport security, SoapUI works just fine. When we configure for Message security, we get an InvalidSecurity error: "An error occurred when verifying security for the message". Our service has a behavior that specifies a certificate as service credentials: <serviceCredentials> <serviceCertificate findValue="CN=SomeCertName" storeLocation="LocalMachine" storeName="My"/> </serviceCredentials> Our .NET clients get the cert in their endpoints in the app.config when we generate service references: <identity> <certificate encodedValue="somebigbase64value==" /> </identity> When we import the wsdl with soapUI, we get all the methods and properties for the service calls, but we cant make a call without getting the error mentioned above. One thing I suspect might be the problem is that our certificate that's being used was not issued by a CA and has no valid trust chain. To get around this with our clients, we have been adding a behavior to the client endpoints to ignore the certificate Validation: <endpointBehaviors> <behavior name="NoTrust"> <clientCredentials> <serviceCertificate> <authentication certificateValidationMode="None"/> </serviceCertificate> </clientCredentials> </behavior> </endpointBehaviors> Our .NET clients manually add this behavior after the service reference has been created. My questions are: 1) Some old posts I saw say that SoapUI does not support wsHttpBinding, is that still the case (even though we see that it works fine with Transport security)? 2) Is there a way to make SoapUI ignore the certificateValidation like we do with our .NET clients Thanks for any help/insight you can provide.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions9.6KViews0likes2CommentsLoading WSDL on test suite open
Hi there, I've created a workspace and project with some interfaces to a SOAP web service of ours. Made a test suite, a test case, some test steps, and all is well. To get the interfaces into SOAPUI, I pointed it at our WSDL on my local dev system (localhost) and it pulled everything in great. Now, I notice that sometimes when I open the project (and the service isn't running on my box), it tries to go out and reload all the WSDL, which can take a bunch of time for everything to time out. When it eventually gives up, I can run my test case and everything works just fine. Is there a way to suppress this re-loading? Chris795Views0likes0CommentsNewb question
Hi there, Just downloaded the LoadUI 2.6.8 trial - we're looking to do load and performance testing of our REST-based web services. I created a web page runner and entered some creds in the settings, and when I click open in browser as a test, things work like I expect. However, when I click "run once", it says it completed, but no traffic actually gets sent across the wire! I watched traffic with fiddler and everything, so I'm a little confused. I'm sure it's something simple I'm missing...anyone have a tip? Thanks, Chris11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes1Comment