ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Monitoring HTTPS Sites Fail with "unrecognized_name" Exception

book

Article ID: 40574

calendar_today

Updated On:

Products

CA Server Automation CA Virtual Assurance for IM

Issue/Introduction

Problem

HTTPS tests fail with the following message in the jcollector.log:

javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name

 

Environment

Supported SRM 5.9 platforms monitoring an HTTPS URL.

 

Cause

Java 7 has certain security enhancements called "Server Name Indication" (SNI). The client (in this case the SRM AIM) must receive a matching hostname from the web server (or virtual web host). If not, Java will not make the connection and throw the SSLProtocolException as noted above.

 

Resolution

Ensure that the target Web Server is configured properly. This will differ based on each environment. However, Apache HTTPD would likely require updates to ServerAlias and/or ServerName within the appropriate *.conf file(s).

 

Additional Information

Java 7 Security Enhancements including "Server Name Indication" (SNI)

Environment

Release: SYSEDG99000-12.9-Stand Alone SystemEDGE Agent
Component:
Powered by Wolken Software