ReadyAPI 3.62.0 JDBC connections failing
Since upgrading ReadyAPi from 3.61.0 to 3.62.0 all of my JDBC test steps, and DB connections using com.microsoft.sqlserver.jdbc.SQLServerDriver are failing with the following error: ERROR: An err...
Forum Discussion
dariazolotko
Staff
StaffHello Jeanette,
Thank you for raising this issue. In ReadyAPI version 3.62, we have updated the JDBC driver, and the newer version forces the SSL connection due to security reasons. As mentioned by one of our contributors, there's a way to disable SSL manually by adding a flag to the connection string: you can update the database connection definition to include the property trustServerCertificate=true. Alternatively, encrypt=false can also be added, but it’s not recommended since it lowers the security.
A note about the described behavior will be added to ReadyAPI documentation soon.
If you still experience issues or need any help, please don’t hesitate to reach out to SmartBear Support Team: https://support.smartbear.com/
Thank you for the update. I understand and appreciate the emphasis on security, especially for external or production-facing systems. However, most of my JDBC connections are used internally within a secure and controlled environment. In these cases, it would be beneficial to have the flexibility to choose whether SSL is required.
While the workaround using trustServerCertificate=true is helpful, it’s not realistic for my setup—I have hundreds of connections, and manually updating each one is not scalable. Ideally, ReadyAPI should offer a configurable option that allows users to enable or disable SSL based on their specific use case and environment.