Configuring The Token Database - Red Hat CERTIFICATE SYSTEM 8.0 - ADMINISTRATION Admin Manual

5.7.4. Configuring the Token Database

The TPS uses an LDAP database called the token database or tokenDB to keep specific information
for each registered token. It also associates tokens with certificates and users.
The token database is viewed or edited through the Administrator tab of the TPS HTML services
page. The agent/admin services page is used to add tokens, check token status, edit token
information, and view token information, like certificates and past operations.
The parameters used to configure the token database in the TPS are listed in
Database Preferences".
Parameter
tokendb.auditLog
tokendb.hostport
tokendb.bindDN
tokendb.bindPassPath
tokendb.templateDir
tokendb.userBaseDN
tokendb.baseDN
tokendb.activityBaseDN
tokendb.certBaseDN
Description
The full path to the audit log file. For example, /var/log/subsystem_name/to
The token database (LDAP) hostname and port number. The format is hostname:
The bind DN to bind to the token database. The default value is cn=directory
The path to a local password file which contains the subsystem passwords. The d
The directory where the templates for the TPS agent page are located.
The LDAP suffix where the user entries are.
The LDAP suffix where the token entries should be added and modified by the TP
The LDAP suffix where the token-based activities should be recorded by the TPS.
The LDAP suffix where the certificate entries should be added by the TPS. The de
Change these templates only to change the appearance of the TPS agent page
• tokendb.indexTemplate
• tokendb.indexAdminTemplate
• tokendb.newTemplate
• tokendb.showTemplate
• tokendb.showCertTemplate
• tokendb.errorTemplate
• tokendb.searchTemplate
• tokendb.searchResultTemplate
• tokendb.searchCertificateResultTemplate
• tokendb.editTemplate
• tokendb.editResultTemplate
• tokendb.addResultTemplate
• tokendb.deleteTemplate
• tokendb.deleteResultTemplate
• tokendb.searchActivityTemplate
Configuring the Token Database
Table 5.10, "Token
159