Token Database; Configuring Tps Logging; Thread Correlation; Tps Configuration Parameters - Red Hat CERTIFICATE SYSTEM 7.3 - ADMINISTRATION Administration Manual

Like configuring multiple subsystem instances, there can be multiple LDAP directories configured.
Additional LDAP parameters, such as the base DN under which to search for entries and the Directory
Server hostname and port, are listed in

8.7. Token Database

The TPS uses an LDAP database called the token database or tokenDB is used to keep specific
information for each registered token. It also associates tokens with certificates and users. The
token database is accessible through the Administrator tab of the TPS HTML services page/ The
agent/admin services page is used to check token status, edit token information, and view token
information, like certificates and past operations. For information on managing the token database,
see the Certificate System Agent's Guide.
The parameters used to configure the token database in the TPS are listed in
Database Preferences".

8.8. Configuring TPS Logging

Log files are configured by changing the relevant lines in the CS.cfg file:
logging.[audit|error|debug].enable=[true|false]
logging.[audit|error|debug]=/var/logs/[filename]
logging.[audit|error|debug].level=[level number]
Log level 0 is least verbose; 10 is most verbose. For example:
[2005-04-29 13:47:08] b65b9828 Upgradeop='applet_upgrade' app_ver='1.2.416DA155'
[2005-04-29 13:47:08] b65b9828 Formatstatus='success' app_ver='1.3.42659461'
[2005-04-29 15:56:06] b65b9828 Enrollmentstatus='success' app_ver='1.3.42659461'
key_ver gives the key set version ID. A key version of 0101 is mapped to the TKS key version
identifier #01#01. cuid gives the card unique identifier, the unique serial number of the smart card.
app_ver gives the applet version number. time gives the elapsed time of the operation.

8.8.1. Thread Correlation

In this example, b65b9828 is the thread ID number. All interactions performed with a particular smart
card are done on a single thread, so the operations all have the same thread ID. In the case where
TPS is interacting with multiple smart cards simultaneously, log messages pertaining to the smart card
operations are interleaved. The thread ID can be used to correlate messages for a single smart card.

8.9. TPS Configuration Parameters

This section outlines all the TPS configuration parameters, their descriptions and valid values that are
typically used for smart card certificate enrollment, key archivals, key recovery, formatting smart cards,
and PIN reset operations.
Table 8.5, "LDAP
new_app_ver='1.3.42659461'
key_ver='0' cuid='40900062FF02000065C5' msn='FFFFFFFF' uid=''
time='45389 msec'
key_ver='0101' cuid='40900062FF020000649D' msn='FFFFFFFF'
uid='Steve Parkinson' time='21058 msec'
Authentication".
Table 8.11, "Token
Token Database
199