2.6. Enterprise Security Client The Enterprise Security Client is a tool for Red Hat Certificate System which simplifies managing smart cards. End users can use security tokens (smart cards) to store user certificates used for applications such as single sign-on access and client authentication. End users are issued the tokens containing certificates and keys required for signing, encryption, and other cryptographic functions. The Enterprise Security Client is the third part of Certificate System's complete token management system. Two subsystems - the Token Key Service (TKS) and Token Processing System (TPS) - are used to process token-related operations. The Enterprise Security Client is the interface which allows the smart card and user to access the token management system. After a token is enrolled, applications such as Mozilla Firefox and Thunderbird can be configured to recognize the token and use it for security operations, like client authentication and S/MIME mail. Enterprise Security Client provides the following capabilities: Supports JavaCard 2.1 or higher cards and Global Platform 2.01-compliant smart cards like Safenet's 330J smart card. Supports Gemalto TOP IM FIPS CY2 tokens, both the smart card and GemPCKey USB form factor key. Supports SafeNet Smart Card 650 (SC650). 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 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). 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/TLS HTTP channel to the back end 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 several different kinds of tokens through default and custom token profiles. By default, the TPS can automatically enroll user keys, device keys, and security officer keys; additional profiles can be added so that tokens for different uses (recognized by attributes such as the token CUID) can automatically be enrolled according to the appropriate profile. Provides information about the current status of the tokens being managed.

Commands: