The message has expired
I installed the current version of SOAP UI on my laptop. When I run any request I get the error message <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault> <faultcode xmlns:ns1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">ns1:MessageExpired</faultcode> <faultstring>The message has expired</faultstring> </soap:Fault> </soap:Body> </soap:Envelope> It used to work well on my desktop. Could you please help me to figure out the problem. Thank you6.6KViews0likes1CommentSOAP UI Return XML Dumping with Invalid Characters
Introduction:Hello Community! I hope I am posting in the correct place. Precursory Information:I am currently using SOAP UI Free to attempt to validate a WSDL. I have a service that looks like this: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header> </SOAP-ENV:Header> <SOAP-ENV:Body> ...SOAP BODY HERE... </SOAP-ENV:Body> </SOAP-ENV:Envelope> This sends out ok, and I get a return message. Precursory Explination: The way myreturn code is designed is to send a response with an XMLattached. I've done research on Request/Reponsewith attachment's in SOAP UI, and it looks like it can do it. I've read the documentation on attachment's, and done additional research on SOAP UI but I cannot find my exact issue. Issue: When returning the XML, I am recieving a bunch of invalid characters, along with a 'dump' of the attached xml. It looks like: ) ) [Invalid Character Here]uuid:XXXXXXX-YYYY-ZZZZ-AAAA-123456789123 <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body/></soapenv:Envelope> [Invalid Character Here]XXXXXXYYYYYYYYYZZZZZZZZZZ11111112222222233333333333/xml ...CORRECT XML THAT IS SUPPOSED TO BE ATTACHED HERE... Note: I am not sure how much I am allowed to share of the code/digits - but the ...CORRECT... is a correct XML I am expecting, and the XYZA and 1234... are all characters that change every time. Is there a way to prepare SOAP UI for this attached XML and not get this dump? I won't be able to validate this the way it is. What I have tried: I have tried adjusting all of the settings in the Request Properties windows with no luck. Has anyone experienced this? Could someone help me prepare my SOAP UI for the attached XML, rather than dump different characters and the contents? Thanks in advance!Solved3.7KViews1like3CommentsHow to transfer TestCase properties value in Authentication(Oauth2.0) Access Token field ?
Here, In "Log in and Update" testcase custom properties present "access_token". I want to transfer this access token value in "get_profile" testStep in Authentication(Oauth 2.0) Access token field. How I do it ? Please reply me .3.7KViews0likes6CommentsHow to set Property Value of Sub Node of XML file in SOAP UI?
Hi Team, Thank you very much in advance. I have xml in the below structure and i need to update values to sub nodes using Groovy script to automate the TestScripts. <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:inb="http://sap.com/xi/FI-Processing"> <soap:Header/> <soap:Body> <inb:OrderItemMessageBulk> <MessageHeader> <CreationDateTime></CreationDateTime> </MessageHeader> <OrderItems> <MessageHeader> <CreationDateTime></CreationDateTime> </MessageHeader> <OrderItem> <DocumentItemID DocumentItemTypeCode="" SendingComponentID="" LogicalSystemID=""> </DocumentItemID> </OrderItems> </inb:OrderItemMessageBulk> </soap:Body> </soap:Envelope> How can i set Value of nodeDocumentItemTypeCode,SendingComponentID andLogicalSystemID in the above XML structure. Kindly guide me to solve the issue. Regards, Ramana.2.7KViews0likes9CommentsHow to increase SOAP UI performace to push more SOAP request in a second.
As part of a process, we need to generate a load of 2.77 SOAP requests per second. I am using Groovy script to run the load with multiple threads and accessing multiple excel files for different data for each unique data. In any way, i am not able to reach transaction rate of 1.7 and above. Inspite of all recommended memory management, my SOAP UI takes minimum 3 seconds for a request. In case of my load, i am not needed to wait for the response, So can Soap ui just submit request and don't wait for a response, thus increase the speed of per second transaction rate. Any help will be greatly appreciated.2.6KViews0likes7CommentsSoap UI 5.3 doesnt work with Selenium 3.0.1 due to apache http jar version mismatch.
Are there versions of Soap UI and Selenium that work together? I tried 5.3 and 3.0.1 but that did not work. The selenium version of http is much more recent that the Soap UI versions. Apparently this is an ongoing problem: https://community.smartbear.com/t5/SoapUI-Open-Source/SoapUI-5-0-0-and-Selenium-WebDriver-2-44-0/td-p/953532.2KViews0likes4CommentsOracle OWSM wss11_message_protection_service_policy Policy -Testing via SOAPUI
Hello, I face an issue testing Web Service has OWSMwss11_message_protection_service_policy Policy, via SOAPUI. I successfully test it via Java Client developed by jDeveloper. But I fail to test it via SOAPUI. As per policy description, OWSMwss11_message_protection_service_policy Policy does the following: It is, message integrity and message confidentiality for inbound SOAP requests in accordance with the WS-Security 1.1 standard. Messages are protected using WS-Security's Basic 128 suite of symmetric key technologies: RSA key mechanisms for message confidentiality , SHA-1 hashing algorithm for message integrity , AES-128 bit encryption. As per my knowledge, we should configure outgoing WS security : Timestamp, Encryption and Signature. I think that the main issueis with the signature part, as we don't need to generate new key, but to use the alreadygenerated key in the encryption part (EncryptedKey)by theprovided server certificate (public key), and then to reference this key in the signature part. so that the main question is that what is the key identifier type to be used in signature config to inform SOAPUI not to generate new key and to use the already existent key generated in the encryption step ? below find successful request message .. as seen,for encryption, forSecurityTokenReference, it usesKeyIdentifier with ValueType=ThumbprintSHA1. and for signing, it refer to the already existentEncryptedKey by usingSecurityTokenReference withReferencewithValueType =EncryptedKey. The question, is how to generate such below sample request with SOAPUI ? <?xml version="1.0" encoding="utf-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsu:Timestamp wsu:Id="Timestamp-yyTgtYX6I5MVLa2FbmoNSQ22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsu:Created>2015-12-13T14:10:21Z</wsu:Created> <wsu:Expires>2015-12-13T14:15:21Z</wsu:Expires> </wsu:Timestamp> <xenc:EncryptedKey Id="EK-ZBxRx8IdiUdW7Ota5jNouA22" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"> <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" /> </xenc:EncryptionMethod> <dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"> <wsse:SecurityTokenReference wsu:Id="STR-8j8GrzYhOwKXqWTXFjmtpQ22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">XfDPshVltIUk3F+ANKhur+qFxs4=</wsse:KeyIdentifier> </wsse:SecurityTokenReference> </dsig:KeyInfo> <xenc:CipherData> <xenc:CipherValue xmime:contentType="application/octet-stream" xmlns:xmime="http://www.w3.org/2005/05/xmlmime"> lNZ4n5U2FZYlwnP82KL/7m3D7sbinTjtOpJ+g0ljZ9vJo+Nrhqu3hCyDDSM168t3liF025fNLmqq +5eZdBR/867in+4x0bVo7OfLPkbCTniynvl79tPM1sFbHd90Y/BANmWr/aQE2Pd7kk73/fOBy3iR vDqRUlHJJZ495qIbU/Y= </xenc:CipherValue> </xenc:CipherData> <xenc:ReferenceList> <xenc:DataReference URI="#_xZrqEzpM6I1zLnNBH0yBUA22" /> </xenc:ReferenceList> </xenc:EncryptedKey> <dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"> <dsig:SignedInfo> <dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> <dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1" /> <dsig:Reference URI="#Timestamp-yyTgtYX6I5MVLa2FbmoNSQ22"> <dsig:Transforms> <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> </dsig:Transforms> <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /> <dsig:DigestValue>BOi0mHMKNIQsBWcUMpiOUp/6jPM=</dsig:DigestValue> </dsig:Reference> <dsig:Reference URI="#Body-6fMgpfle8G2QmdAMdzKW8w22"> <dsig:Transforms> <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> </dsig:Transforms> <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /> <dsig:DigestValue>Hd3355tAsYR16ElYPQkapb3eVl0=</dsig:DigestValue> </dsig:Reference> </dsig:SignedInfo> <dsig:SignatureValue>HqRqFeDXs6XyzKnXn40ux9JGuLg=</dsig:SignatureValue> <dsig:KeyInfo> <wsse:SecurityTokenReference> <wsse:Reference URI="#EK-ZBxRx8IdiUdW7Ota5jNouA22" ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey" /> </wsse:SecurityTokenReference> </dsig:KeyInfo> </dsig:Signature> </wsse:Security> </soap:Header> <soapenv:Body wsu:Id="Body-6fMgpfle8G2QmdAMdzKW8w22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <xenc:EncryptedData Type="http://www.w3.org/2001/04/xmlenc#Content" Id="_xZrqEzpM6I1zLnNBH0yBUA22" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc" /> <dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"> <wsse:SecurityTokenReference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:Reference URI="#EK-ZBxRx8IdiUdW7Ota5jNouA22" ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey" /> </wsse:SecurityTokenReference> </dsig:KeyInfo> <xenc:CipherData> <xenc:CipherValue xmime:contentType="application/octet-stream" xmlns:xmime="http://www.w3.org/2005/05/xmlmime"> qChK3cVSFbAGOW6N4UDFLIIBZOAWERhy75wCVtOhuDoUVPlqJtTpZnJd7e3eAPKzC8UGtngjOg5t VRWaeowi2qrzySAsfJYBhhRKrDnZR77t8g/6LG0B9ZfFjsF4lAnytUx7OYkfiyvudZRQXa9EBCXx IvATkIN4+hliQbLYT/qx9+SIFPtPyF2zgFLJXp0IXURJwtjegJA5P3HFlci8JQjNizgoQtHUx9KO Kpa/i4SKsTZ3/QsEKiQvCPhVVV1A5pc2h2hHCQpHTklb0+dDh8A5kTHs5rBJEjcfeYLAskrFbZdk rlDQUHe4wuiDDJoVHPoqhYURwacbyaNtbzEKI3yU/+uzi4SzGuptP0lMlnfQDdNxeF4Bztnm4+df I3qW </xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </soapenv:Body> </soapenv:Envelope>2.1KViews0likes2Commentssoap ui error while using wcf with wshttpbinding for Kerberos authentication
Hi, Using Soap UI as a client accessing the WCF service with the wshttpbindingwith the below configuration: <wsHttpBinding> <binding name="Binding1" receiveTimeout="00:30:00" sendTimeout="00:30:00" closeTimeout="00:30:00" openTimeout="00:30:00" maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647"> <security mode="TransportWithMessageCredential"> <message clientCredentialType="Windows" negotiateServiceCredential="false" establishSecurityContext="false" /> </security> </binding> </wsHttpBinding> We need to authenticate using the Kerberos token but we are getting the below error: <s:Fault> <s:Code> <s:Value>s:Sender</s:Value> <s:Subcode> <s:Value xmlns:a="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">a:InvalidSecurity</s:Value> </s:Subcode> </s:Code> <s:Reason> <s:Text xml:lang="en-GB">An error occurred when verifying security for the message.</s:Text> </s:Reason> </s:Fault> I tried the following way from the websites such as : 1.wss-passwordtype to passwordtext 2.https://www.soapui.org/soap-and-wsdl/spnego/kerberos-authentication.html ,I referred thi ssite and made all the changes. But nothing works. Can you please help to fix this issue.1.7KViews0likes0CommentsSOAP UI - Set Proxy Settings Using -t in CMD Execution
Also posted here: https://stackoverflow.com/questions/59102194/soap-ui-set-proxy-settings-using-t-in-cmd-execution I am getting nowhere with the documentation on this topic. So far, I know the execution command is "-t" for setting the proxy settings, BUT, I cannot get the proxy settings to actually be set. In other words, the command line query looks like this: "cmd /C CD C:\Program Files\SmartBear\SoapUI-5.2.1\bin & testrunner.bat -c""TestCase"" ""SOAP_QUERY.XML"" -S -P""UserName=UsernameTest"" -P""Password=PasswordTest"" -t""autoProxy_TrueOrFalse=False"" -t""activateProxy_TrueOrFalse=True"" -t""proxy_Host=ProxyAddress"" -t""proxy_Port=ProxyPort"" -t""proxy_Username=ProxyUsername"" -t""proxy_Username=ProxyPassword"" -P""OutPutDumpFileLocation=OutPut.XML"" -e ""https://EndPoint"" -r > ""ExecutionLog.Txt" Obviously, the values I provided are not those text values - I put the actual details in there. Example, ProxyPort could be 8080. I know the XML for the settings of the proxy looks like this: <con:soapui-settings xmlns:con="http://eviware.com/soapui/config"> <con:setting id="ProxySettings@autoProxy">XYZ</con:setting> <con:setting id="ProxySettings@enableProxy">XYZ</con:setting> <con:setting id="ProxySettings@host">XYZ</con:setting> <con:setting id="ProxySettings@port">XYZ</con:setting> <con:setting id="ProxySettings@username">XYZ</con:setting> <con:setting id="ProxySettings@password">XYZ</con:setting> </con:soapui-settings> BUT, I don't know if this goes into the query OR directly in the settings file and then you can parametrize it like this: <con:soapui-settings xmlns:con="http://eviware.com/soapui/config"> <con:setting id="ProxySettings@autoProxy">${#Project#autoProxy_TrueOrFalse}</con:setting> <con:setting id="ProxySettings@enableProxy">${#Project#activateProxy_TrueOrFalse}</con:setting> <con:setting id="ProxySettings@host">${#Project#proxy_Host}</con:setting> <con:setting id="ProxySettings@port">${#Project#proxy_Port}</con:setting> <con:setting id="ProxySettings@username">${#Project#proxy_Username}</con:setting> <con:setting id="ProxySettings@password">${#Project#proxy_Password}</con:setting> </con:soapui-settings> I even tried to modify the command line query like: "cmd /C CD C:\Program Files\SmartBear\SoapUI-5.2.1\bin & testrunner.bat -c""TestCase"" ""SOAP_QUERY.XML"" -S -P""UserName=UsernameTest"" -P""Password=PasswordTest"" -t""ProxySettings@autoProxy=False"" -t""ProxySettings@enableProxy=True"" -t""ProxySettings@host=ProxyAddress"" -t""ProxySettings@port=ProxyPort"" -t""ProxySettings@username=ProxyUsername"" -t""ProxySettings@password=ProxyPassword"" -P""OutPutDumpFileLocation=OutPut.XML"" -e ""https://EndPoint"" -r > ""ExecutionLog.Txt" Please if anyone has experience in creating this command line execution PLEASE HELP ME.1.2KViews0likes0CommentsSoap UI with External JAR not working as it works in Eclipse
Hello All, Here is my problem. My client has asked to use their custom RestClient for some scenarios where we test the RESTful services. For this purpose, i have build a custom JAR with the code relating to their RestClient and placed it under..bin/ext folder. Then i tried to call the function from Groovy Script to access the custom rest client. I am getting an weird exception which is not happening if put the same JAR under the build project of the Java project and execute them through Eclipse. Will the groovy script not work the same way the Eclipse works if we do the above steps? Exception Logged : Wed Apr 13 12:58:11 IST 2016:ERROR:java.lang.IllegalAccessError: tried to access method sun.net.www.protocol.http.AuthenticationInfo.getProxyAuth(Ljava/lang/String;I)Lsun/net/www/protocol/http/AuthenticationInfo; from class sun.net.www.protocol.http.PopcornHttpURLConnection1.2KViews0likes2Comments