Configuring Ssl Connections With The Tps - Red Hat CERTIFICATE SYSTEM 8.0 - MANAGING SMART CARDS WITH THE ENTERPRISE SECURITY CLIENT 1-23-2010 Manual

Managing smart cards with the enterprise security client
Table of Contents

Advertisement

File or Directory
components/
chrome/
defaults/
esc
xulrunner/
Table 6.7. Enterprise Security Client File and Directory Locations on Red Hat Enterprise Linux

6.2. Configuring SSL Connections with the TPS

By default, the TPS communicates with the Enterprise Security Client over standard HTTP. It may be
desirable to protect the TPS-client communications by using HTTP over SSL (HTTPS).
1. The Enterprise Security Client has to have the CA certificate for the CA which issued the
TPS's certificates in order to trust the TPS connection. Import the CA certificate as described in
Section 3.6.4, "Importing CA
2. The Enterprise Security Client needs to be configured to communicate with the TPS over SSL; this
is done by setting the Phone Home URL, which is the default URL the Enterprise Security Client
uses to connect to the TPS.
Resetting the Enterprise Security Client's Phone Home URL is described in more detail in
Section 3.3, "Configuring Phone
a. Open the Enterprise Security Client.
b. Insert a new, blank token into the machine.
Purpose
XPCOM components.
Directory for Chrome components and additional
application files for Enterprise Security Client
XUL and JavaScript.
Enterprise Security Client default preferences.
The script which launches the Enterprise
Security Client.
Privately-deployed XULRunner directory.
Certificates".
Home".
Configuring SSL Connections with the TPS
61

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the CERTIFICATE SYSTEM 8.0 - MANAGING SMART CARDS WITH THE ENTERPRISE SECURITY CLIENT 1-23-2010 and is the answer not in the manual?

Questions and answers

Table of Contents