RHEL 6 Smart Card Admin - Chapter 4. Using the Enterprise Security Client

PayloadBooks.com

Red Hat Enterprise Linux 9 Essentials Book now available.

Purchase a copy of Red Hat Enterprise Linux 9 (RHEL 9) Essentials

Red Hat Enterprise Linux 9 Essentials Print and eBook (PDF) editions contain 34 chapters and 298 pages

Chapter 4. Using the Enterprise Security Client

4.1. Launching Enterprise Security Client

4.2. Overview of Enterprise Security Client Configuration

4.2.1. Enterprise Security Client File Locations
4.2.2. About the Preferences Configuration Files
4.2.3. About the XUL and JavaScript Files in the Enterprise Security Client

4.3. Configuring Phone Home

4.3.1. About Phone Home Profiles
4.3.2. Setting Global Phone Home Information
4.3.3. Adding Phone Home Information to a Token Manually
4.3.4. Configuring the TPS to Use Phone Home

4.4. Using Security Officer Mode

4.4.1. Enabling Security Officer Mode
4.4.2. Enrolling a New Security Officer
4.4.3. Using Security Officers to Manage Users

4.5. Configuring SSL Connections with the TPS

4.6. Customizing the Smart Card Enrollment User Interface

4.7. Disabling LDAP Authentication for Token Operations

The following sections contain basic instructions on using the Enterprise Security Client for token enrollment, formatting, and password reset operations.

4.1. Launching Enterprise Security Client

There are two concepts for launching the Enterprise Security Client. The Enterprise Security Client process must be started and it runs silently, waiting to detect any inserted smart card or token. The user interface for the Enterprise Security Client opens automatically when smart cards are inserted or can be opened manually.

Initiate the Enterprise Security Client daemon (escd) from the command line:

esc

This daemon listens silently for smart cards and opens the GUI as soon as a smart card is inserted.

To open the Enterprise Security Client GUI manually, click Applications, System Tools, and then Smart Card Manager.