20 years of SoapUI - Share your story
For two decades, it’s been part of how teams learned API testing, a tool people built with, debugged through, and leaned on to get things done. We’d love to hear from those of you who’ve used it — whether it helped you solve a problem, learn something new, or just left you with a memorable story. Tell us about your experience! - SmartBear
SOAPUI 5.9.1 Still Includes Log4j 2.17.1 — When Will an Updated Version Be Released?
Hello Team, We are currently working through remediation of Log4j vulnerabilities in our environment. As part of this effort, we downloaded and installed the latest available SOAPUI Open Source version (5.9.1). However, after installation, we observed that the Log4j library bundled with SOAPUI is still version 2.17.1. Our internal security scanners continue to report vulnerabilities for Log4j and require us to upgrade to Log4j 2.25.3 or later, but SOAPUI does not appear to include that updated version. We would appreciate clarification on the following: Is Log4j 2.17.1 considered vulnerable within the context of SOAPUI Open Source, or is it considered safe/supported by SmartBear in this product? If it is not vulnerable in this context, can this be safely ignored or suppressed from a security standpoint? If it is considered vulnerable, is there an upcoming SOAPUI Open Source release planned that includes Log4j 2.25.3 or newer? If no such release is planned, could you provide recommended remediation steps (for example, instructions for upgrading or replacing the Log4j libraries manually, if supported)? Currently, we are unable to meet security compliance requirements because SOAPUI 5.9.1 continues to ship with Log4j 2.17.1. Any guidance on timelines or supported workarounds would be greatly appreciated. Thank you.
Unable to authenticate license in Ready API Login button unresponsive
Ughhh! 3 hours wasted now. Uninstalled the latest Ready API and reinstalled. 3 days in a row now I have had to login to activate my ready api license. Today the button Login DOES NOT WORK ..so I am completely locked out of the application. The login button is completely unresponsive. No window opens to login. I am expecting a browser to open up and to login .. but nothing happens. Any suggestions / alternate paths to get authenticated?
SSL Keystore Request Property not working since 3.6.2
Hello Community, up until updating to Version 3.6.2/3.6.3 i had no complications using the request property for SOAP requests "SSL Keystore". I used it either via environment properties or with the explizit configured keystore name f.e. When downgrading to 3.6.1 the client authentification works fine. With 3.6.2 and 3.6.3 ReadyAPI is not sending any client auth information to the server. So here is my question. What changed? Am i missing a new property or configuration i did not find in the update history? Best regards
Shared workspace
Hi, I have a couple-three dozen Projects, stored on a Google Drive, that i want to share with a couple co-workers, such that we are all working off the same song sheet. I have shared the google drive folder where they all reside, with them, but is there a way to allow them to import all the Projects into their SoapUI in one swell foop? Has seen something about shared Workspace, but can't find anything about how to accomplish that. Can anyone suggest?
SoapUI 5.9.0 Installer.app does not open on macOS Ventura 13.7.5
Hello, I’m trying to install SoapUI 5.9.0 Open Source on my MacBook Pro (Intel) running macOS Ventura 13.7.5. Java 11 (Temurin) is installed and works correctly (java -version shows version 11.0.28). However, when I try to launch the SoapUI 5.9.0 Installer.app from the DMG package, macOS shows the message: “The application ‘SoapUI 5.9.0 Installer.app’ can’t be opened” The icon is displayed with a “prohibited” sign. It seems like the installer is not recognized as compatible, even though release notes mention Ventura compatibility starting from version 5.7.1. Is there an updated installer for macOS Ventura (Intel)? Should I use the .tar.gz / .zip distribution instead of the DMG? Has this issue been officially confirmed for Ventura users? Thanks in advance for any guidance.
How to escape ampersand in Property Expansion?
Hi, In our TestCases, we use properties as values for SOAP requests in the following way: <com:name>${#TestCase#currentName}</com:name> This mostly works fine, but in some cases the property values contain an ampersand (&) character. This then leads to an incorrect XML and thus invalid SOAP Request: <com:name>Fencing & Security</com:name> The expected behaviour would be that SoapUI escapes the invalid character to create the following element: <com:name>Fencing & Security</com:name> When assigning the value to the element using a separate Property Transfer test step, this is correctly done (the value is escaped). The problem is that we set all the properties using a Groovy Script before running the request, which makes using property expansion in the request by far the easiest way to assign all values. Is there a way to use property-expansion that does escape special characters when used in XML?No Fluff, Just Real Stuff - DevRel Newsletter July edition here!
Hi everyone, The latest issue of No Fluff, Just Real Stuff, our DevRel newsletter, is here! In this edition, we’re talking about the launch of the SmartBear MCP server, share the latest release update information for SoapUI, and a link to our recent Contract Testing: Debunking the Doubts webinar and much more. As always, we hope you find it’s packed with useful updates and practical insights! Got feedback or want to be featured in a future edition? Drop us a line at devrel@smartbear.com —we’d love to hear from you. Enjoy the read! —Frank, Jo & Yousaf. The SmartBear DevRel Team
