Prepare for TLS server certificate validation
- Last Updated: November 11, 2026
- 5 minute read
- MOVEit Automation
- Version 2025.1
- Documentation
MOVEit Automation strengthens TLS server certificate validation for connections between MOVEit Automation clients and servers. This change affects Web Admin, Java API and COM API connections, command-line clients and utilities, and other MOVEit Automation operations that establish affected server connections, including Failover and ASx scenarios.
Connections that previously succeeded despite certificate errors can fail after an upgrade. Before upgrading, review the connections in your MOVEit Automation environment and verify that the server certificates and connection settings meet the certificate validation requirements.
What is changing?
Server certificate validation is enabled by default for affected clients. If a certificate cannot be validated, the connection fails unless certificate errors are explicitly ignored using the configuration option available for that client.
Certificate validation can fail when:
- The certificate is expired or not yet valid.
- The certificate is not trusted.
- The certificate chain is incomplete or invalid.
- The hostname or IP address used for the connection does not match an identity in the certificate.
Before you upgrade
Review the connections between MOVEit Automation clients and servers before upgrading.
- Identify the hostname or IP address used by the client to connect to the server.
- Verify that the server certificate is valid and trusted.
- Verify that the certificate chain is valid.
- Verify that the hostname or IP address used for the connection matches an identity in the server certificate.
- If the certificate cannot be validated, correct the certificate, trust chain, or connection name where possible.
- Check local connection names. ASx helper connections and
GetMICConfig.exeuse the local computer's short name. Ensure that the certificate is valid for the name used by these connections. A certificate that contains only the fully qualified domain name might not be sufficient.
When reviewing certificate configuration, consider the name or address that each client uses to connect to the MOVEit Automation server, including fully qualified domain names (FQDNs), short host names, and IP addresses. Verify that the hostname or IP address used for the connection matches the certificate Subject or Subject Alternative Name (SAN).
Affected components
Review certificate validation for the following components and scenarios:
- Web Admin connections to MOVEit Automation servers.
- Java API connections.
- COM API connections.
- Command-line clients and utilities, including
GetMICConfig. - Failover connections.
- ASx connections and related operations identified in the upgrade guidance.
- Unattended or automated processes that use an affected client.
The REST API is not affected by this certificate-validation change.
Web Admin connections
Web Admin validates certificates when connecting to configured MOVEit Automation backend servers. For environments in which Web Admin connects to multiple Automation servers, review each configured backend connection individually.
Verify that the hostname or IP address configured for each backend connection is valid for the certificate presented by that server.
If certificate errors must be ignored for a particular backend, Web Admin provides configuration for specifying the servers to which the exception applies. Refer to the Web Admin documentation for the configuration settings, config.properties.
Certificate trust for Web Admin and Java clients
Web Admin and Java API/CLI clients use the Windows certificate store to establish trust in the MOVEit Automation server certificate. Ensure that the required issuing CA root and intermediate certificates are available to the account that runs the applicable client.
Establishing certificate trust does not bypass certificate validity or server-name checks.
API connections
Review applications and integrations that use the Java API or COM API, or native C++ API to connect to MOVEit Automation. Existing applications might continue to compile but fail to connect if the server certificate cannot be validated.
The Java and COM clients provide options for controlling certificate-error handling. If an existing integration cannot validate the server certificate, update the certificate or connection configuration where possible. If certificate errors must be ignored, use the certificate-validation option provided by the applicable API.
For configuration details, see the Java API or COM API documentation.
Command-line clients and utilities
MICentralAPIJavaClient.jarMICentralClt.exeGetMICConfig.exe
If certificate errors must be ignored, use the IgnoreCertErrors (draft link for review
pruposes: IgnoreCertErrors )option for the affected command or
utility. Configure the exception only where required and correct the certificate, trust, or
connection-name issue where possible.
Failover
Review certificate validation when MOVEit Automation is configured for Failover. The certificate-validation changes can affect connections used in a Failover environment.
Before upgrading, verify the certificates and connection names used by the Failover configuration. Ensure that the certificates can be validated using the hostname or IP address configured for the applicable connection.
After upgrading, verify connectivity and replication, and perform the planned Failover role-switch checks for both nodes. A successful Web Admin connection or a working standalone node does not confirm that Failover connections are operating correctly.
ASx
The certificate-validation changes can also affect applicable AS1, AS2, and AS3 (ASx) operations. These operations use a local TLS connection between MOVEit Automation and the ASx helper.
Before upgrading, verify that the certificate used for the local helper connection is valid for the local computer name used by the connection. This validation is separate from certificates used with external ASx partners.
If an exception is required for the local helper connection, use the applicable local certificate-error configuration.
Local connections
Certificate validation also applies to affected local connections. The Ignore
certificate errors for local connections setting in the Configuration Utility
applies to local connections that use this setting, including the local ASx helper connection,
GetMICConfig.exe, and COM API applications that connect to the local MOVEit
Automation server.
A local certificate-error exception does not apply to remote connections. Configure certificate-error exceptions separately for remote connections using the option provided by the affected client.
Ignoring certificate errors
Affected clients provide mechanisms for explicitly allowing a connection when certificate validation would otherwise fail.
Where possible, correct the underlying certificate, certificate trust, certificate chain, or connection-name issue instead of routinely configuring the client to ignore certificate errors.
If you choose to ignore certificate errors, configure the exception only for the connections where it is required, using the option provided by the affected client.
Express install
Express Install generates a self-signed certificate and enables Ignore Certificate Errors for the Web Admin backend connection that it creates. Other affected clients still require their own valid certificate configuration or an explicit client-specific exception.
Express Install is not recommended for production use. For production, use a valid, trusted certificate, configure matching names and trust for every connection, and remove unnecessary certificate-error exceptions.
After upgrading
After upgrading, verify the connections used in your MOVEit Automation environment. In particular, verify Web Admin connections, Java API and COM API integrations, command-line clients and utilities, Failover, ASx operations, and any unattended processes that rely on affected connections. For ASx deployments, test the applicable AS1, AS2, or AS3 operations rather than relying on a successful standard file-transfer task. For Failover deployments, verify peer connectivity, replication, and the planned role-switch scenarios for both nodes.
If a connection fails because certificate validation cannot be completed:
- Verify the hostname or IP address being used for the connection.
- Verify that the certificate is valid for that hostname or IP address.
- Verify the certificate validity period.
- Verify the certificate chain and trust configuration.
- Correct the certificate, trust, or connection configuration where possible.
- If the connection must be allowed despite certificate validation errors, configure the applicable client to ignore certificate errors.