TLS server certificate validation changes

MOVEit Automation now strengthens TLS server certificate validation for connections between MOVEit Automation clients and servers. Web Admin, Java API, COM API, and command-line clients now validate server certificates by default.

Connections that previously succeeded despite certificate errors can now fail. This can occur if a certificate is not trusted, is expired or not yet valid, has an incomplete or invalid certificate chain, or does not include the hostname or IP address used for the connection. A certificate issued by a trusted certificate authority can still fail validation if the name used for the connection does not match an identity in the certificate. This change can affect Web Admin access, API integrations, scripted or command-line operations, Failover, AS1/AS2/AS3 operations, and configuration-export jobs.

Before upgrading, review the connections used in your MOVEit Automation environment and verify that the appropriate certificates, connection names, and trust configuration meet the new validation requirements. Where possible, correct certificate, trust-chain, or connection-name issues rather than configuring clients to ignore certificate errors.

For important pre-upgrade information, affected components, and configuration options, see Prepare for TLS server certificate validation.

TLS certificate validation for failover communications

Failover communications now use TLS certificate validation by default. When failover servers use self-signed certificates or certificates that cannot be validated, administrators can enable the Ignore certificate errors option in the Failover configuration.

For more information, see Failover Tab.