Red Hat CERTIFICATE SYSTEM 8.0 - ADMINISTRATION, Admin Manual

Page: 41 / 564

Enterprise Security Client
19
• Supports JavaCard 2.1 or higher cards and Global Platform 2.01-compliant smart cards like
Safenet's 330J smart card
• Supports Global Platform 2.01-compliant smart cards like Gemalto e-gate 32K and Gemalto TOP IM
FIPS CY2 64K tokens, both the smart card and GemPCKey USB form factor key.
• Enrolls security tokens so they are recognized by TPS.
• Maintains the security token, such as re-enrolling a token with TPS.
• Provides information about the current status of the token or tokens being managed.
• Supports server-side key generation so that keys can be archived and recovered on a separate
token if a token is lost.
The Enterprise Security Client is a cross-platform client for end users to register and manage keys
and certificates on smart cards or tokens. This is the final component in the Certificate System token
management system, with the Token Processing System (TPS) and Token Key Service (TKS).
NOTE
For more information on using the Enterprise Security Client, see the
Certificate System
Enterprise Security Client Guide
.
The Enterprise Security Client provides the user interface of the token management system. The end
user can be issued security tokens containing certificates and keys required for signing, encryption,
and other cryptographic functions. To use the tokens, the TPS must be able to recognize and
communicate with them. Enterprise Security Client is the method for the tokens to be enrolled.
Enterprise Security Client communicates over an SSL HTTP channel to the backend of the TPS. It is
based on an extensible Mozilla XULRunner framework for the user interface, while retaining a legacy
web browser container for a simple HTML-based UI.
After a token is properly enrolled, web browsers can be configured to recognize the token and use it
for security operations. Enterprise Security Client provides the following capabilities:
• Allows the user to enroll security tokens so they are recognized by the TPS.
• Allows the user to maintain the security token. For example, Enterprise Security Client makes it
possible to re-enroll a token with the TPS.
• Provides support for two types of tokens.
UserKey
identifies token keys for an individual. The
simpler
DeviceKey
identifies the key itself, without verifying an individual's identity.
• Provides information about the current status of the tokens being managed.