What's New in ReadyAPI

Applies to ReadyAPI 3.53, last modified on June 07, 2024
Important Notice for ReadyAPI Customers

ReadyAPI has fully transitioned to the ID-based SmartBear License Management (SLM) system. We strongly encourage users still utilizing file-based licensing, including key-based and ProtectionLS floating licenses, to migrate before the September 1, 2024 deadline to avoid commercial impact. Please be aware that support for file-based licensing has ended and technical support is no longer available, which may lead to unresolved technical issues.

If you cannot migrate from file-based licensing before September 1, 2024, it is crucial to contact your SmartBear representative immediately to align with our deprecation plans and avoid disruptions. Additionally, retaining file-based licenses for any solution expansions or renewals after this date will result in a service charge of up to 30% of the renewal or expansion invoice value to cover the extension costs. To avoid these charges, please initiate your migration now.

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.

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 readyapi-install.vmoptions to 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.

See Also

Version History

Download ReadyAPI
Highlight search results