Chapter 8. Token Processing System

Chapter 8. Token Processing System

8.1. Working with Multiple Instances of a Subsystem
8.1.1. Configuring Failover Support
8.1.2. Configuring Multiple Instances for Different Functions
8.2. Formatting Smart Cards
8.3. Resetting the Smart Card PIN
8.4. Applet Upgrade
8.5. Enrolling Smart Cards through the Enterprise Security Client
8.5.1. Enabling SSL in the TPS
8.5.2. Server-Side Key Generation and Archival of Encryption Keys
8.5.3. Smart Card Certificate Enrollment Profiles
8.5.4. Automating Encryption Key Recovery
8.5.5. Symmetric Key Changeover
8.5.6. Setting Token Types for Specified Smart Cards
8.6. Configuring LDAP Authentication
8.7. Token Database
8.8. Configuring TPS Logging
8.8.1. Thread Correlation
8.9. TPS Configuration Parameters
8.9.1. TKS Configuration File Parameters

The Token Processing System (TPS) serves as the conduit between the Enterprise Security Client and the other subsystems (CA, TKS, DRM) in the Certificate System and is the only means for the client to communicate with the other subsystems. It provides the following functionalities for users managing their smart cards through the Enterprise Security Client:

The TPS must be configured to work with two Certificate System subsystems: the CA, which will process all of the certificate enrollment and revocation requests initiated through the Enterprise Security Client, and the Token Key Service, which generates a master key which is used to derive secret keys specific to each smart card, which are used to wrap (encrypt) the certificates and commands transmitted between the TPS and the client. The TPS can be optionally configured to work with a DRM instance, which will perform server-side key generation and key archival and recovery for the keys and certificates stored on the smart cards.

After the TPS is configured (Section 2.6.3, “Configuring a TPS”), it is operational. It is possible to further customize the TPS for specific deployments. This chapter explains how to customize the TPS instance.

NOTE

Unlike the other subsystems, the TPS does not have a Java™-based Console to change configuration parameters. The TPS configuration file, CS.cfg, must be edited directly. For more information on editing the CS.cfg file, see Section 3.6.2, “Editing the Configuration File”.