09-13-2017 09:11 AM - edited 09-13-2017 11:47 AM
I just learned of SoapUI in a roundabout fashion, and I'm glad I did. It did in seconds what had so far swallowed up two days of trying to understand WSDL and XSD files, and then spit out a complete request document, which is what I really wanted in the first place. No fault of the program, I got this:
>The message could not be processed. This is most likely because the action '[changedurl].com/ServiceContract/V2/IDataIntegrationContract/ImportData' 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
Ok, so... I assume the "mismatch between bindings" is unlikely because I just downloaded the WSDL. The URL in there 404's, is that a problem? And what token is this referring to? This is purely HTTP, but there is a wspolicy that I am not competent to read.
UPDATE: it was not clear on the display, but the error is actually "BadContextToken" I see many references to this in google as being a problem in SoapUI and various suggestions on how to fix it on the server - thing is, I didn't write the server. Is there some way to fix this on the UI side?
09-13-2017 12:14 PM
Thank you for your post!
Did you try switching to BasicHttpBinding instead of WCF? WCF uses wsHttpBinding by default which can use certain WS-Security types that we do not support.
SOAP WS* Standards: https://support.smartbear.com/readyapi/docs/projects/requests/ws/index.html
09-13-2017 12:34 PM
Thanks Nastya, where do I find this setting?
I looked through most of the SoapUI Preferences before posting but did not see this. I see some settings in WS-I about the SecurityProfile, but that doesn't seem to be related.
09-14-2017 12:54 AM
I recommend that you open a new support case: https://support.smartbear.com/message/?prod=ReadyAPI
and provide us with your project file (or WSDL)so we can better understand your requirements.