Red Hat CERTIFICATE SYSTEM 7.2 - ADMINISTRATION Administration Manual page 191

Parameter
auth.instance.n.retryConnect
auth.instance.n.baseDN
auth.instance.n.ui.title.en
auth.instance.n.ui.description.en
auth.instance.n.ui.id.UID.name.en
auth.instance.n.ui.id.PASSWORD.name.en
auth.instance.n.ui.id.UID.description.en
auth.instance.n.ui.id.PASSWORD.description.en
Table 7.5. LDAP Authentication
Parameter
channel.encryption
Table 7.6. Encrypted Channels Between the TPS and Tokens
Operation can be enroll, PIN reset, or format. n is an integer.
Parameter
op.Operation.mapping.order
op.Operation.mapping.n.filter.tokenType
op.Operation.mapping.n.filter.tokenATR
TPS Configuration Parameters
Description
The number of times the TPS tries to reconnect
to the LDAP server after a connection attempt
fails. The valid values are integers. For example,
3.
The base DN from which to start the LDAP
search. For example, o=example.com.
The title of the LDAP authentication plug-in. For
example, LDAP Authentication.
The description of the LDAP authentication
activity. For example, This authenticates
the user against the LDAP dev
directory.
The UID parameter name. For example, LDAP
User ID.
The password parameter name. For example,
LDAP Password.
The description of the UID parameter.
The description of the password parameter.
Description
Sets whether the data being transmitted between
the TPS and the token is to be encrypted. The
valid values are true|false.
Description
The order of the mappings. The format is n,n,n.
For example, 0,1,2. These mapping IDs must
be defined in op.Operation.mapping.n
parameters, where n is one of the mapping IDs
specified in the order.
The filter based on the tokenType sent by
the Enterprise Security Client. This is the
expected tokenType that TPS will receive
from the Enterprise Security Client. For
example, userKey. The target tokenType
will be matched if the tokenType sent by the
Enterprise Security Client also matches.
The filter based on the ATR sent by the
Enterprise Security Client. This is the expected
ATR that the TPS will receive from the Enterprise
Security Client. For example, 1234. The target
tokenType will be matched if the ATR of the
token and the ATR mentioned here matches.
171