Important Notice for ReadyAPI Customers
ReadyAPI has fully transitioned to the ID-based SmartBear License Management (SLM) system. We are now moving into the final phase of deprecation of file-based licenses. Customers still using file-based licensing need to plan for migration to SLM before September 30, 2025.
If you are still in the process of migrating or have yet to start, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, please log a request with our Customer Care Team, who are standing by to help.
For further information and timelines, please refer to this 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.
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.
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.
We updated Spring to version 5.3.33.
Please see here for a list of fixes included in this patch.