Looking at Smart Card Certificate Enrollment Profiles
191
8.5.2.3. Step 3: Configuring the TPS to Generate and Archive Keys
1. Stop the TPS.
/etc/init.d/
instance_ID
stop
2. Edit the following parameters in the TPS
CS.cfg
file to use the appropriate DRM connection
information:
conn.drm.totalConns=1
conn.drm1.hostport=
DRM_HOST:DRM_SSLPORT
conn.drm1.clientNickname=Server-Cert
conn.drm1.servlet.GenerateKeyPair=/kra/GenerateKeyPair
conn.drm1.servlet.TokenKeyRecovery=/kra/TokenKeyRecovery
conn.drm1.retryConnect=3
conn.drm1.SSLOn=true
conn.drm1.keepAlive=false
3. Also edit the smart card profiles in the TPS
CS.cfg
file.
The TPS
CS.cfg
file has a section defining each type of smart card profile to maintain. In the
default configuration, the
userKey
is defined under the
op.enroll.userKey
subsection. The
keyGen
subsection of the
userKey
profile defines each type of key/certificate pair allowed for that
type of smart card. In the default configuration, one of the key/certificate pairs is
encryption
. Set
the following parameters to enable server-side key generation and to archive keys:
op.enroll.userKey.keyGen.encryption.serverKeygen.enable=true
op.enroll.userKey.keyGen.encryption.serverKeygen.drm.conn=drm1
op.enroll.userKey.keyGen.encryption.serverKeygen.archive=true
op.enroll.userKey.keyGen.encryption.serverKeygen.encryptPrivKey=true
4. Restart the TPS subsystem.
/etc/init.d/
instance_ID
restart
8.5.3. Looking at Smart Card Certificate Enrollment Profiles
The CA subsystem has four default smart card enrollment profiles which the TPS is configured, by
default, to use:
• caTokenUserEncryptionKeyEnrollment.cfg
• caTokenUserSigningKeyEnrollment.cfg
• caTempTokenUserEncryptionKeyEnrollment.cfg
• caTempTokenUserSigningKeyEnrollment.cfg
The profile configuration files are in the
/var/lib/
instance_ID
/profiles/ca/
directory.
Administrators have the ability to customize these profiles. For instance, a profile could be edited to
include the user's email address in the Subject Alternative Name extension. The email address for the
user is retrieved from the authentication directory. To configure the CA for LDAP access, change the
following parameters in the profile files, with the appropriate directory information:
Содержание CERTIFICATE SYSTEM 7.3 - ADMINISTRATION
Страница 1: ...Red Hat Certificate System 7 3 Administration Guide Publication date May 2007 updated March 25 2010 ...
Страница 15: ...xv Index 525 ...
Страница 16: ...xvi ...
Страница 38: ...Chapter 1 Overview 16 Figure 1 4 Certificate System Architecture ...
Страница 82: ...Chapter 2 Installation and Configuration 60 rpm ev rhpki manage ...
Страница 154: ...132 ...
Страница 194: ...172 ...
Страница 238: ...216 ...
Страница 244: ...222 ...
Страница 246: ...224 ...
Страница 286: ...264 ...
Страница 292: ...270 ...
Страница 318: ...Chapter 13 Certificate Profiles 296 Parameter IssuerType_n IssuerName_n ...
Страница 321: ...Freshest CRL Extension Default 299 Parameter PointName_n PointIssuerName_n ...
Страница 371: ...Configuring Mappers 349 Figure 15 9 Selecting a New Mapper Type 6 Edit the mapper instance and click OK ...
Страница 398: ...376 ...
Страница 412: ...390 ...
Страница 472: ...450 ...
Страница 500: ...Appendix A Certificate and CRL Extensions 478 Parameter namen Table A 8 IssuerAlternativeName Configuration Parameters ...
Страница 506: ...484 ...
Страница 528: ...506 ...
Страница 546: ...524 ...