Configuring SSL between Symantec Endpoint Protection Manager and the clients

Article:HOWTO81056  |  Created: 2012-10-24  |  Updated: 2014-09-21  |  Article URL http://www.symantec.com/docs/HOWTO81056
Article Type
How To


Subject


Configuring SSL between Symantec Endpoint Protection Manager and the clients

Symantec Endpoint Protection Manager uses an Apache web server to communicate with clients and provide reporting services. The web server uses HTTP for all communications. HTTP is an unencrypted protocol and does not provide for the confidentiality or integrity of the communications over it. You can configure the Symantec Endpoint Protection Manager Apache web server to use a Secure Sockets Layer (SSL) certificate to sign and encrypt data using an HTTPS connection.

Table: Configuring SSL communication to the client

Step

Action

Description

1

Check that the default SSL port is available

By default, SSL traffic uses port 443. In some networks, port 443 may already be bound to another application or service. Before you enable SSL communication, you must check to see if the default port is available.

See Verifying port availability.

2

Change the default SSL port as needed

If port 443 is not available, choose an unused port from the high port range (49152-65535). Configure the management server to use the new port. Update the management server list to reflect the new port.

See Changing the SSL port assignment in Symantec Endpoint Protection Manager.

See Configuring a management server list.

3

Enable SSL communication to the client

Edit the Apache httpd.conf file to allow SSL communication to the client. Test the SSL connection, and then switch the clients to HTTPS communication.

See Enabling SSL for the Apache web server for client communication.

See Managing the client-server connection.


Legacy ID



v57069738_v81626096


Article URL http://www.symantec.com/docs/HOWTO81056


Terms of use for this information are found in Legal Notices