SoapUI-5.7.0 OpenJDK 16.0.2 Vulnerability / Update
Hello All, I am a system administrator and my development team is using the latest SoupUI-5.7.0 and its getting flagged in our vulnerability analysis system as needing to update "OpenJDK to a version greater than 7u311 / 8u302 / 11.0.12 / 13.0.8 / 15.0.4 / 16.0.2" showing that the current installed version is16.0.1 2021-04-20. Can I update OpenJDK without compromising SoapUI-5.7.0 and or is there an update for SoapUI that will address this issue in the future? If so, can where can I find the information on that or the timeline so that I can monitor for its release?SoapUI long term issues
Hi, I have been using SoapUI for a while with a view to recommending it and ReadyAPI to the company as our default SOAP and REST api tool. However there are some fundamental problems that seem to have been around on the forums for a while that I would like further information on if possible. By the way I am using version 5.7.0: WSDL refresh - SoapUI often gets itself into a state where a service Update Definition will always fail with a message that includes the phrase "a[c] is null". Saving the project, closing SoapUI, restarting SoapUI and performing another Update Definition will be successful. Adding requests to operations - Often either adding a new request or cloning an existing rest on an operation will create the request, but it never appears in the tree beneath the operation and there is no way to refresh the tree. The only way I have found to select the new request is to select the same operation in the mock service and right-click Open Request and then choose the new request. The only way to see the request under the operation is to once again saving the project, close SoapUI, and restart SoapUI. Mock service caching - I have also had a few occasions where a mock service will return old responses rather than an updated one, as if it were cached. This is infrequent and harder to reproduce consistently, but stopping the mock service and restarting it makes no difference, and again only saving the project, closing SoapUI, restarting SoapUI, restarting the mock service and make the request again will get the expected response. Documentation - The online documentation is quite light. I found this to be particularly true for mock service operation dispatching, where a few more examples would help, and a full API for the build in objects such as requestContext. Also a link to the APIs for the items that can be imported would be useful. Forum - There doesn't appear to be much forum activity, and I haven't noticed much interaction from SmartBear employees. Cheers, Chris
SOAPUI log4J vulnerability
We upgraded to 5.7 however our scans are still flagging a security issue with LOG4J. I thought 5.7 would have corrected this as the release notes indicate the new jar files are included. I physically checked the server and I do in fact see the log4j-1.2.15 and not the 2.17 versions. Any advice? Path : C:\Program Files\SmartBear\SoapUI-5.7.0\hermesJMS\lib\log4j-1.2.15.jar Installed version : 1.2.15
soapUI 5.6.0. java.lang.NoSuchMethodError with Java12
Hi, sind last week we used soapUI 5.4. with Java8 Now we made a update to soapUI 5.6.0. After installation of Java12 AdoptOpenJdK soapUI writes an error: [exec] SoapUI 5.6.0 TestCase Runner [exec] Configuring log4j from [/usr/gasx/R00/jenkins/dev-tools/soapui-5.6.0_20200715/bin/soapui-log4j.xml] [exec] 12:54:18,641 INFO [SoapUI] Adding [/usr/gasx/R00/jenkins/dev-tools/soapui-5.6.0_20200715/bin/ext/mariadb-java-client-2.6.1.jar] to extensions classpath [exec] 12:54:18,642 INFO [SoapUI] Adding [/usr/gasx/R00/jenkins/dev-tools/soapui-5.6.0_20200715/bin/ext/ojdbc6.jar] to extensions classpath [exec] Exception in thread "main" java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlOptionsBean.isLoadDTDGrammar()Z [exec] at org.apache.xmlbeans.impl.common.SAXHelper.saxFactory(SAXHelper.java:70) [exec] at org.apache.xmlbeans.impl.common.SAXHelper.newXMLReader(SAXHelper.java:46) [exec] at org.apache.xmlbeans.impl.store.Locale.getSaxLoader(Locale.java:3073) [exec] at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1272) [exec] at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1259) [exec] at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345) [exec] at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:252) [exec] at com.eviware.soapui.config.SoapuiSettingsDocumentConfig$Factory.parse(SoapuiSettingsDocumentConfig.java:59) [exec] at com.eviware.soapui.DefaultSoapUICore.initSettings(DefaultSoapUICore.java:259) [exec] at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:141) [exec] at com.eviware.soapui.DefaultSoapUICore.<init>(DefaultSoapUICore.java:132) [exec] at com.eviware.soapui.tools.AbstractSoapUIRunner.createSoapUICore(AbstractSoapUIRunner.java:216) [exec] at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:192) [exec] at com.eviware.soapui.tools.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:137) [exec] at com.eviware.soapui.tools.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:112) [exec] at com.eviware.soapui.tools.SoapUITestCaseRunner.main(SoapUITestCaseRunner.java:122) SoapUI runs on Redhat 7.8 and openjdk version "12.0.2" 2019-07-16 OpenJDK Runtime Environment AdoptOpenJDK (build 12.0.2+10) OpenJDK 64-Bit Server VM AdoptOpenJDK (build 12.0.2+10, mixed mode, sharing) The Fix inhttps://community.smartbear.com/t5/SoapUI-Open-Source/Soap-UI-5-6-0-tgz-on-Linux-is-broken-FIX-INSIDE/m-p/204960#M30957don't work - and I don't know why the normal release of soapUI has this bug. Can you help me? Best Regards from Germany, Michael
SoapUI 5.6.0 (Thanks!)
I have no clue what they did, but version 5.6.0 is running smooth when using a Mac. I have had not yet had any session that was jammed. I even could run all my tests automatic sequential. This 5.6.0 is a relief compared to 5.5.0 and previous versions (since 4.6.0). I am very satisfied with this version!😀
How to reproduce this message signature in code
Hi guys, I have had a tough time solving this puzzle, according to the above configuration SoapUI should sign the whole message as described in the documentation here Unfortunately, this description doesn't align with the SignedInfo node in the soap message, where it appears to sign only the message body, as apparent from the Reference tag and Id pointing to the body Id. I tried doing it with different combinations without any luck. If I sign only the message body the digest and Signature value don't match with that of SoapUI. Then I also tried signing the whole soap envelope but that too doesn't work. Even if it is the whole message, which parts does it include, like the Headers, Binary Security Token, TimeStamp and body or only the TimeStamp and body. The digest changes with every request. I hope someone also got this issue and found a way out, if yes please let me know. Thank you!Failed to update interface when updating wsdl definition
Hi. I am using SoapUI Open Source v5.6.0. When I update a wsdl, the error ‘Failed to update interface: [com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException]’ is being returned. Looking at the error log: Thu Jan 11 09:19:26 EST 2024:ERROR:com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlInterfaceDefinition.load(WsdlInterfaceDefinition.java:52) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext.loadDefinition(WsdlContext.java:62) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext.loadDefinition(WsdlContext.java:34) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.cacheDefinition(AbstractDefinitionContext.java:245) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.access$400(AbstractDefinitionContext.java:47) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:218) at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46) at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:131) at java.base/java.lang.Thread.run(Thread.java:835) Other people in my office using SoapUI are not having an issue with this wsdl. I am not sure if this is related, but the environment recently had its’ Tomcat version updated, and I was testing with this wsdl before the update. When I try to create a new request, I am just getting the envelope, header, body and endpoint name. None of the definition. When I use the ‘Recreate a default request from the schema’ icon, I am getting the same skeleton request. Any ideas? Thank you. Angie
