TDM SMTP Error - "Could not convert socket to TLS"

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

When attempting to send automated emails from CA Test Data Manager (TDM) following a job execution, the application fails to deliver the notification. The following error is displayed:

Could not convert socket to TLS

 

 

Environment

 All supported versions of TDM Portal. 

Cause

1. Certificate Trust Issues: The SMTP server's security certificate is not trusted by the Java truststore used by TDM.
2. Hostname Mismatch: The destination host name configured in TDM does not match the 'Common Name' (CN) or 'Subject Alternative Name' (SAN) on the server’s SSL/TLS certificate.
3. TLS Protocol Conflict: The mail server uses TLS, but the handshake fails because the client cannot verify the identity of the server via the provided DNS alias.

Resolution

To resolve the connection failure, verify and update the email configuration settings as follows:

1. Identify the Server Hostname: Determine the exact host name for which the SMTP server's security certificate was issued (e.g., smtp-server-01.example.com instead of a generic alias like mail.example.com).
2. Update TDM Configuration:
   • Log in to the TDM configuration interface.
   • Navigate to the Email Settings/Configuration section.
   • Change the Destination Host (or SMTP Host) from the generic DNS alias to the specific Server Host Name identified in Step 1.
3. Validate the Connection:
   • Save the configuration changes.
   • Trigger a test email or re-run a job to confirm that the TLS/SSL handshake error is eliminated.

By aligning the destination host setting with the server's identity on the security certificate, the Java truststore can successfully validate the connection. This ensures secure communication and enables the successful delivery of automated notifications.