ContributionsMost RecentMost LikesSolutionsRe: Web Services - WS Security (Decryp and Sig) for responsesSOAPUI Support team - Any suggestions?Re: Web Services - WS Security (Decryp and Sig) for responsesIt's not a good idea to have one key store for every key. However, for testing I tried to do what you said. So I made two copies of the keystore. From first I deleted the client's public key and from second I deleted the provider's private key. Then I added the keystores to SoapUI. It added the store with private key but when I added the store that only had the public key, SoapUI complained that <error: java.security.KeyStoreException: No private keys found in keystore!>. Please advise. I want to provide some more information like screen shots etc. but I can't do that here as this is an open forum. Can you please provide me your email address and I can email you those. Also, if you can provide a phone number then it will help to resolve this issue faster. This process is taking lot of time.Re: Web Services - WS Security (Decryp and Sig) for responsesThanks for your reply. From Outgoing WS-Security Configurations tab, I see options for setting security for Encryption and Signature where I can specify which keys to use for encryption and signing the message. However, for Incoming WS-Security Configurations tab, I only see option for specifying key store, there is no option to specify the keys. See screen shot 1. So for decryption, even if we specify the keystore that needs to be used for decryption and signature validation, how will we specify which keys to be used for decryption and signature validation? In our case, we have only one keystore with two keys. Key1 (our private key) and Key2 (web service provider public key). For Outgoing we use Key1 for signing and Key2 for encryption. For Incoming, we want to specify use Key1 for decryption and Key2 for signature verification? Any documentation/suggestions that how to accomplish this?Web Services - WS Security (Decryp and Sig) for responsesWe use SOAP UI for testing all our services. Our external services are secured using WS-Security (X509), encrypting and signing the message content. - Consumer encrypts the message with Service public key and then signs the message with Consumer's private key - The service then validates the signature using consumer's public key and decryps the message using Service's private key - The service then processes the request and prepares the response for sending - The service then encrypts the message with Consumer's public key and signs the message with Service's private key - The consumer then validates the signature with Service's public key and decrypts the message with it's private key We're trying to setup SOAP UI to test these secured services and are trying to do following - 1. For request (Outgoing): SOAP UI encrypts the request message with Service public key and signing the message with Consumer's private key 2. For response (Incoming): SOAP UI validates the signature with Service's public key and decrypts the message with consumer's private key We're able to do #1 above that is adding encrypting and signature for outgoing message. Bur for response XML, we're unable to add details for signature validation and decryption, and SOAP UI shows the response in decrypted form. So the question is that how can we set WS-Security (Signature validation and Decryption settings) for response (Incoming message) so that we can see the actual response (and not cryptic response). Refer to following article that lists setting up WS-Security - http://www.soapui.org/SOAP-and-WSDL/applying-ws-security.html Refer to Section 3 Outgoing WSS and Section 4 Incoming WSS. Please note that Section 3 refers to Encryption and Signature but Section 4 does not provide this information. I want to understand how to setup security for responses.Re: Issues with WS call when adding HTTP parm Transfer-EncodingThank you for your reply. One thing I had not set was "Chunking Threshold" in the global HTTP Settings. As soon as I set that I started to get the responses. So I think this was an configuration issue and not a defect. I tried with few values for "Chunking Threshold" and both of these worked fine. Thanks for your help.Issues with WS call when adding HTTP parm Transfer-EncodingIssues with WebService call when adding HTTP parameter Transfer-Encoding=true We use WebSphere Enterprise Service Bus (WESB) for developing and publishing the web services. We're able to test these web services using SoapUI 4.0. But on adding HTTP parameter Transfer-Encoding=true, the web service started to return following error message - <soapenv:Fault><faultcode></faultcode><faultstring>Illegal chunk length digit: 60</faultstring><detail></detail></soapenv:Fault> We opened a bug with IBM for this as a WESB defect. After analysing the issue with TCP dump and other application server logging, IBM came back and told that the client application is not sending the correct chunked data format. Please work with the application code, which is creating and sending the incorrect chunked data. Following reason was provided by IBM. We can see the request coming in ? [8/18/11 13:47:31:812] 0000006a HttpRequestMe [setRequestURL: set URI to /mywebservice/export] .. > [8/18/11 13:47:31:828] 0000006a WASAxis2Servl.doPost() [Entry] .. ? [8/18/11 13:47:31:857] 0000006a HttpServiceCo [Reading body, chunked] .. ? [8/18/11 13:47:31:858] 0000006a HttpServiceCo [Client sent a bad chunk: 60] From the IP trace - 0000 00 1a 64 96 e6 a5 00 30 f2 ea 5b fc 08 00 45 00 ..d....0..[...E. 0010 00 56 92 20 40 00 7e 06 58 1a 0a 03 e9 4b 0a 03 .V. @.~.X....K.. 0020 15 16 0b ca 25 8f f5 3f 98 df 34 74 d7 89 50 18 ....%..?..4t..P. 0030 fc 00 45 d4 00 00 4d 69 44 61 74 61 3e 0a 20 20 ..E...Mi Data>. 0040 20 3c 2f 73 6f 61 70 65 6e 76 3a 42 6f 64 79 3e </soapenv:Body> 0050 0a 3c 2f 73 6f 61 70 65 6e 76 3a 45 6e 76 65 6c .</soapenv:Envel 0060 6f 70 65 3e ope> The chunk should end with OD OA OD OA value which it is missing. This issue is very critical to us for our testing. Can you please look into this and do the needful.Re: StringToObjectMap: Update endpoint urlHi, Thanks for the reply. We are able to get it working. I am still seeing some performance issues. We have to allocate lot of memory & we have some constraints on that. When we run the TestCase from UI I see property called Discard Successful Test Step Results to Preserve Memory. Is there way I can pass it using the StringToObjectMap. Regards ParamStringToObjectMap: Update endpoint urlHi, I am using SOAPUI API's for running the projects using WsdlProjectRunner. Constructor of this class takes two parameters one is SOAPUI Project and another one is StringToObjectMap. I want to override the end point URL for all requests in the projects. I specified the following parameters for the map and used it. It still not taking the new endpoint url I specified in the MAP. I have the following questions. I don't see any documentation around the values that I can pass in the Map. 1). Can I used the Map to update the endpoint url for all teststeps in the project. I am using the following code to run it WsdlProject project = new WsdlProject(PropertyUtil.getProperty("projectFilePath")+testExcelFiles); StringToObjectMap paramsMap = new StringToObjectMap(); paramsMap.put("e", PropertyUtil.getProperty("regressionEndPointURL")); WsdlProjectRunner runner = new WsdlProjectRunner(project , paramsMap); System.out.println("^^^^ New End Point URL is::"+PropertyUtil.getProperty("regressionEndPointURL")); runner.run(); List<TestSuiteRunner> suiteResults = runner.getResults(); generateReport(suiteResults); I even tried with the following parameters for the map and still seeing the same result. It's not taking new url. It's still getting executed with the old url. paramsMap.put("-e", PropertyUtil.getProperty("regressionEndPointURL")); paramsMap.put("Endpoint", PropertyUtil.getProperty("regressionEndPointURL")); Regards ParamRe: XPATH Assertions not working propertly with CDATA.Sent SoapUI Project through email.Re: XPATH Assertions not working propertly with CDATA.I have included the second part of my problem described. The XPATH Assertions with CDATA behave differently when run from a test suite rather than a test step. Screen shots and xmls attached. you could compare with TestStep Run vs TestSuite run. Please email me or call me for further clarifications, as i need to come with an alternate solution ASAP. Your timely help on this regard will be greatly appreciated. i am open for a webex or similar sessions if required to demonstrate the problem if required.