CAUAJM_E_20387 HTTPS Client: SSL handshake with host <server1.example.com> failed: self-signed certificate in certificate chain.
search cancel

CAUAJM_E_20387 HTTPS Client: SSL handshake with host <server1.example.com> failed: self-signed certificate in certificate chain.

book

Article ID: 446476

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

Customer configured agent and manager with HTTPS. Now autoping against the machine gives an error:

CAUAJM_I_50023 AutoPinging Machine server1.example.com
CAUAJM_E_90036 Communication attempt with the AutoSys Agent has failed! Resource identifier [https://server1.example.com:8888].
CAUAJM_E_20387 HTTPS Client: SSL handshake with host server1.example.com failed: self-signed certificate in certificate chain.
CAUAJM_E_50281 AutoPing from the Scheduler WAS NOT SUCCESSFUL.

CAUAJM_E_90036 Communication attempt with the AutoSys Agent has failed! Resource identifier [https://server1.example.com:8888].
CAUAJM_E_20387 HTTPS Client: SSL handshake with host server1.example.com failed: self-signed certificate in certificate chain.
CAUAJM_E_50283 AutoPing from the Application Server WAS NOT SUCCESSFUL.

CAUAJM_E_50026 ERROR: AutoPing WAS NOT SUCCESSFUL.

 

Cause

This is because agent's keystore was setup using Broadcom internal certificates, and so has a self-signed certificate issued by: Issuer: CN=wa-internal-root, O=Broadcom Inc., L=San Jose, ST=California, C=US"    

This can be verified by issuing a curl / openssl test against the Agent's URI  from the manager host.

Example: curl -k -v https://server1.example.com:8888 

Verify the certificate present in that URL above.

Resolution

  • If the Agent (agent's receiver keystore) can be configured a valid vendor/trusted issuer certificate, that manager can recognize, the above error should disappear
  • If the Agent(agent's receiver keystore) can only be configured with Self Signed certificate, then change below to false on the manager's $AUTOUSER/sslconfig.$AUTOSERV file


ServerCertificateVerification=false 

  • Restart Application Server + Scheduler and then retest autoping again. It should succeed now.

Additional Information

Refer to this link for more information about this parameter.

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.