ESP workstation failed to open connection through a secure AT-TLS connection

Products

• ESP Workload Automation

Issue/Introduction

 The workstation fails to connect to any of the ESP subsystem ports that are now secured via AT-TLS through PAGENT. "Failed to open a connection!". 

Error Information from ESP Workstation trace:

14:20:41.599:[receive][###.##.##.##: ####] [creating WSSecureSocket]
14:20:41.699:[winsock][###.##.##.##: ####] [Connect: IsConnected]
14:20:41.842:[winsock][###.##.##.##: ####] [WSSecureSocket::SubscribeConnection - Error occured:]
14:20:41.842:[winsock][###.##.##.##: ####] [SSL_connect rc: -1, ERR_get_error() rc: 337047686, SSL_get_error() rc: 1]
14:20:41.842:[winsock][###.##.##.##: ####] [SSL VERSION: OpenSSL 1.1.1s  1 Nov 9999, SSL ERROR: SSL_ERROR_SSL]
14:20:41.842:[winsock][###.##.##.##: ####] [error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed]
14:20:41.842:[winsock][###.##.##.##: ####] [WSSecureSocket - Certificate verification failed with rc: 62]
14:20:41.843:[winsock][###.##.##.##: ####] [done]

 

Environment

Component: ESP Workload Automation
Release:   12.0

Resolution

Return code 62 was caused by the mismatched hostname.   The same IP address or DNS name should be used on the Workstation connection manager.

Reference: TLS Encryption for ESP Workstation Server and Client

 

Additional Information