Automic Agent fails to connect to the JCP: Error: U02000313 No subject alternative DNS name matching found

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

An Automic Agent fails to connect to the Automation Engine. The agent log shows the following error:

U02000313 Communication error with partner '####:8443', error: '(certificate_unknown) No subject alternative DNS name matching #### found.'

Environment

• Automic Workload Automation 24.x and higher

Cause

The Agent attempts to connect to the Java Communication Process (JCP) using a hostname (typically a short name) that is not included in the Subject Alternative Name (SAN) field of the JCP's SSL certificate.

Resolution

Troubleshooting Steps

Method 1: Update Agent Configuration

1. Open the agent's configuration file (ini).
2. Locate the connection= parameter in the [TCP/IP] section.
3. Change the hostname to the Fully Qualified Domain Name (FQDN) that is already listed in the JCP certificate's SAN field.
4. Restart the agent.

 

Method 2: Re-issue the JCP Certificate

1. Generate a new Certificate Signing Request (CSR) for the JCP.
2. Ensure the Subject Alternative Name (SAN) field includes all variations of the server's identity used by agents, including:
   • Short hostname
   • Fully Qualified Domain Name (FQDN)
   • IP Address (if applicable)
3. Import the new certificate into the JCP keystore.
4. Restart the JCP and the Agent.