search cancel

Content is blocked when viewing the Web console after installing a self-signed certificate

book

Article ID: 154976

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

After configuring the Symantec Endpoint Protection Manager (SEPM) Tomcat and IIS servers to use SSL, you are prompted to Show Content when attempting to log in using the Web Console.

The following error is displayed in a dialog box when attempting to log in to the SEPM Web console:

Content was blocked because it was not signed by a valid security certificate. For information, see Certificate error in Internet Explorer help.

Cause

This problem happens because the SEPM Web console automatically resolves the SEPM server Fully Qualified Domain Name (FQDN) or hostname to its corresponding IP address. If the self-signed certificate is signed against the FQDN or hostname of the SEPM server, then your browser will attempt to block the content.

Resolution

This problem is fixed in Symantec Endpoint Protection 11 Release Update 7 Maintenance Patch 2 (RU7 MP2). For information on how to obtain the latest build of Symantec Endpoint Protection, read Obtaining the latest version of Symantec Endpoint Protection or Symantec Network Access Control.

Note: This document is for the specific problem outlined in the Cause section above. The same behavior happens when using an improperly created certificate, or when your Public Key Infrastructure (PKI) is not configured correctly. PKI problems must be resolved before the SEPM Web console will display properly.