Red Hat CERTIFICATE SYSTEM 7.3 - ADMINISTRATION, Administration Manual

Page: 226 / 554

Chapter 8. Token Processing System
204
Parameter Description
auth.instance.
n
.retryConnect 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
.
auth.instance.
n
.baseDN The base DN from which to start the LDAP
search. For example,
o=example.com
.
auth.instance.
n
.ui.title.en The title of the LDAP authentication plug-in. For
example,
LDAP Authentication
.
auth.instance.
n
.ui.description.en The description of the LDAP authentication
activity. For example,
This authenticates
the user against the LDAP dev
directory
.
auth.instance.
n
.ui.id.UID.name.en The UID parameter name. For example,
LDAP
User ID
.
auth.instance.
n
.ui.id.PASSWORD.name.en The password parameter name. For example,
LDAP Password
.
auth.instance.
n
.ui.id.UID.description.en The description of the UID parameter.
auth.instance.
n
.ui.id.PASSWORD.description.en The description of the password parameter.
Table 8.5. LDAP Authentication
Parameter Description
channel.encryption Sets whether the data being transmitted between
the TPS and the token is to be encrypted. The
valid values are
true|false
.
Table 8.6. Encrypted Channels Between the TPS and Tokens
Operation
can be enroll, PIN reset, or format.
n
is an integer.
Parameter Description
op.
Operation
.mapping.order 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.
op.
Operation
.mapping.
n
.filter.tokenType 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.
op.
Operation
.mapping.
n
.filter.tokenATR 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.