Forum Discussion

MaartenR's avatar
MaartenR
Occasional Visitor
10 days ago
Solved

Issue with connections (self-signed certificates?) after upgrading to 3.63.0

Hi everyone,

I have test projects that send XML messages to a system using self-signed certificates.
After upgrading to version 3.63.0, this no longer works.

When I downgrade back to 3.61.0, everything works fine.

Does anyone know what could be causing this issue in version 3.63.0?

Kind regards,
Maarten

  • From the SSL section of the ReadyAPI docs:

    https://support.smartbear.com/readyapi/docs/en/configure-requests/authentication/ssl-client-auth.html

    “Planned Changes to Trust Manager in ReadyAPI 3.63.0 and 3.64.0” — the new version introduces more granular controls for handling self-signed certificates.

    Under Preferences → SSL, there's a new interface for viewing/untrusted certificates and whitelisting them.

    So: previously ReadyAPI might have implicitly trusted self-signed certs (or more loosely accepted them), but 3.63.0 begins shifting toward stricter certificate trust handling. That aligns exactly with your symptom: it worked in 3.61.0, fails in 3.63.0.

    Let me know if that helps!

1 Reply

  • From the SSL section of the ReadyAPI docs:

    https://support.smartbear.com/readyapi/docs/en/configure-requests/authentication/ssl-client-auth.html

    “Planned Changes to Trust Manager in ReadyAPI 3.63.0 and 3.64.0” — the new version introduces more granular controls for handling self-signed certificates.

    Under Preferences → SSL, there's a new interface for viewing/untrusted certificates and whitelisting them.

    So: previously ReadyAPI might have implicitly trusted self-signed certs (or more loosely accepted them), but 3.63.0 begins shifting toward stricter certificate trust handling. That aligns exactly with your symptom: it worked in 3.61.0, fails in 3.63.0.

    Let me know if that helps!