CLewis
Occasional Contributor
Joined 18 years ago
User Profile
User Widgets
Contributions
- 3.6KViews0likes0Comments
Re: Insert file as base64 into request
I figured there was probably some way to do it - learn something every day. In any case I will email you the code - feel free to review and improve as necessary, or ignore all together. Currently it inserts the file at the cursor, I'm not sure if this is ideal or not. Thanks, Cory3.6KViews0likes0CommentsInsert file as base64 into request
We have some webserivces that accept base64 binary files in the request. Ideally we'd like a way to insert files, converted to base64, at specified position within the request. I am not aware of a current way to do this in soap-ui. So, I wrote the functionality to do this, adding a new option to the right click window in the request editor pane. I'd be more than happy to contribute this back(I previously provided the Response SLA assertion). Ole, let me know if you(or anyone else) is interested, and the best way to do so. I don't remember how we did it before. Thanks, Cory7.4KViews0likes4CommentsRe: X.509 Cert Failing Triple AAA
Are you using the Verify step in datapower to secure the messages, or an AAA step? What's the actual error DP gives you? The verify step is pretty flexible - you can try a different signature type. We generally use Subject Key Identifier. If you have a requirement to use BST, though, that doesn't help much.2.4KViews0likes0Comments2.5 Beta - WS-Security SKI Change
Just tried out 2.5 beta. All of our WS-Security configurations use SKI. In 2.5, I get the following error now: Wed Oct 01 11:12:05 EDT 2008:ERROR:An error occured [An unsupported token was provided (An X509 certificate with version 3 must be used for SKI. The presented cert has version: 1)], see error log for details Error log: Wed Oct 01 11:12:05 EDT 2008:ERROR:org.apache.ws.security.WSSecurityException: An unsupported token was provided (An X509 certificate with version 3 must be used for SKI. The presented cert has version: 1) org.apache.ws.security.WSSecurityException: An unsupported token was provided (An X509 certificate with version 3 must be used for SKI. The presented cert has version: 1) at org.apache.ws.security.message.token.SecurityTokenReference.setKeyIdentifierSKI(SecurityTokenReference.java:272) at org.apache.ws.security.message.WSSecSignature.prepare(WSSecSignature.java:404) at org.apache.ws.security.message.WSSecSignature.build(WSSecSignature.java:721) at com.eviware.soapui.impl.wsdl.support.wss.entries.AddSignatureEntry.process(AddSignatureEntry.java:168) at com.eviware.soapui.impl.wsdl.support.wss.OutgoingWss.processOutgoing(OutgoingWss.java:156) at com.eviware.soapui.impl.wsdl.submit.filters.WssRequestFilter.filterWsdlRequest(WssRequestFilter.java:54) at com.eviware.soapui.impl.wsdl.submit.filters.AbstractRequestFilter.filterAbstractHttpRequest(AbstractRequestFilter.java:35) at com.eviware.soapui.impl.wsdl.submit.filters.AbstractRequestFilter.filterRequest(AbstractRequestFilter.java:29) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:116) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) So am I out of luck here?2.4KViews0likes2CommentsPretty Print project xmls?
Would it be possible to save the project xmls with "pretty print"? I ask because we have an automated monitor tool built around soap-ui. Developers create their test cases and check them into CVS, which are pulled onto the test machine by ant. The problem is that when using ws-security, the keystore paths are absolute and have to be replaced. This isn't an issue if there's only one. . I have a regex to do it. However the regex doesn't work correctly when there are multiple, because they are all on the same "line". . .as is a large percentage of the configuration file. I can fix it by hand and putting each element on a seperate line. Thanks, Cory2.6KViews0likes3CommentsUpdate Definition updates requests it shouldn't
Using 2.0 Pro final, we've found that Update Definition, when only "Create New Requests" is checked(and there may be other combinations), sometimes still updates existing requests. Sometimes it will wipe entire requests, replacing it with the default request. Mostly, though, it just adds missing elements. The least occurring result is that it does what I want. For example, a snippet from one of my requests, before definition update: <doc:requestHeader> <doc:requestor>soap-ui</doc:requestor> </doc:requestHeader> After an update(which didn't actually have any changes in it) <doc:requestHeader> <doc:businessTransactionId>?</doc:businessTransactionId> <doc:requestor>soap-ui</doc:requestor> <doc:responseRequired>?</doc:responseRequired> <doc:transactionEffectiveDateTime>?</doc:transactionEffectiveDateTime> <doc:transactionId>?</doc:transactionId> <doc:transactionSubmitDateTime>?</doc:transactionSubmitDateTime> </doc:requestHeader> It also does this even when I don't check any of the check boxes on the update definition dialog.2.3KViews0likes3Comments