Features Added to ReadyAPI 3.53.0
Important Notice for ReadyAPI Customers
Starting from ReadyAPI 3.62.0, VirtServer 3.29.0, and TestEngine 1.34.0, SmartBear Product Family has fully deprecated file-based licenses and transitioned to the ID-based SmartBear License Management (SLM) system. Any customers still using file-based licenses must complete their migration to SLM by September 30, 2025.
From October 1, 2025, existing and activated file-based licenses will continue to work for some time. However, SmartBear will no longer generate new file-based licenses or support activation and deactivation of file-based licenses in ReadyAPI, VirtServer, or TestEngine. All new and updated licenses are now issued in SLM only.
All technical support for file-based licenses has now ceased, and SmartBear no longer maintains the file-based licensing system. Any access or service issues will result in service disruptions that we will not be able to restore.
If you have not completed the process of migrating, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, log a request with our SmartBear Support, who are standing by to help.
For further information and timelines, refer to the File-Based License End-of-Life Policy page.
ReadyAPI 3.53.0 includes a few changes compared to the previous product version – ReadyAPI 3.52.0. For information on the changes made to other versions, see Version History.
SLM On-premise License Server for OIDC/Okta
We added support for Client Credentials to TestRunners and Docker to facilitate SLM On-premise License Server 2.0 and later. This requires configuring the SLM On-premise License Server for OIDC/Okta for client credentials to work.
ReadyAPI Feature Enhancement
Users can use a file named
vmoption virtserver.oidc.login.timeoutto specify JVM options that ReadyAPI will incorporate post-installation. The file must be in the same directory as the ReadyAPI installer.In the ReadyAPI PKCE flow for logging into Virtserver, there is a timeout of 20 seconds. ReadyAPI waits for 20 seconds for the browser to open, for users to enter authorization credentials, and for Okta to redirect back to ReadyAPI. If this process exceeds 20 seconds, ReadyAPI displays the Login Screen again with the "Login with OIDC" button. This timeout value can be configured via the
vmoption virtserver.oidc.login.timeout.
General Updates
We updated Spring to version 5.3.33.
Please see here for a list of fixes included in this patch.