![Red Hat CERTIFICATE SYSTEM 7.3 - ADMINISTRATION Скачать руководство пользователя страница 214](http://html.mh-extra.com/html/red-hat/certificate-system-7-3-administration/certificate-system-7-3-administration_administration-manual_1427433214.webp)
Chapter 8. Token Processing System
192
policyset.set1.p1.default.params.dnpattern=UID=$request.uid$, O=Token Key User
policyset.set1.p1.default.params.ldap.enable=true
policyset.set1.p1.default.params.ldap.basedn=ou=people,dc=host,dc=example,dc=com
policyset.set1.p1.default.params.ldapStringAttributes=uid,mail
policyset.set1.p1.default.params.ldap.ldapconn.host=localhost.example.com
policyset.set1.p1.default.params.ldap.ldapconn.port=389
These CA profiles come with LDAP lookup disabled by default. The ldapStringAttributes parameter
tells the CA which LDAP attributes to retrieve from the company directory. For example, if the directory
contains uid as an LDAP attribute name, and this will be used in the subject name of the certificate,
then uid must be listed in the ldapStringAttributes parameter, and request.uid listed as one of the
components in the dnpattern.
8.5.4. Automating Encryption Key Recovery
The Certificate System allows for a semi-automated recovery if a user loses, destroys, or misplaces
a token. The TPS automatically recovers the appropriate encryption keys and certificates for a
permanently or temporarily lost token, depending on the circumstances of the token loss. To prevent
misuse of the recovery feature, the TPS requires that a user must have a single active token.
When a user loses a token, the user must first get a replacement token. If a new enrollment is
attempted with this new token, the TPS blocks the enrollment since the user already has an active
token.
The token status in the database must be changed to
lost
. This action is performed through the TPS
agent services page. The TPS agent, after affirmatively identifying the user, can search for the user's
ID in the
Search tokens
link. The TPS agent select the active token and update the status, with the
appropriate reason to recover the key.
•
This token has been physically damaged.
Used if the token is known to be destroyed.
•
This token has been permanently lost.
Used if the token is lost or stolen, so the key is compromised.
The certificates on the token are revoked
•
This token has been temporarily lost.
Used if the token is mislaid. The certificates on the token are
revoked
There are two different schemes for recovery:
GenerateNewKey
, to create a new key and certificate,
and
RecoverLast
, to recover the last encryption key and associated certificate.
The user can enroll for a replacement token. It is preferred that signing keys be generated on the
smart card and not archived so that if the smart card is lost, new signing keys and certificates must be
regenerated on the token, and temporary certificates created. The definition for which keys should be
regenerated and which keys should be recovered is set in the following TPS
CS.cfg
parameters:
• For damaged tokens:
op.enroll.userKey.keyGen.recovery.destroyed.keyType.num=2
op.enroll.userKey.keyGen.recovery.destroyed.keyType.value.0=signing
op.enroll.userKey.keyGen.recovery.destroyed.keyType.value.1=encryption
op.enroll.userKey.keyGen.signing.recovery.destroyed.revokeCert=true
op.enroll.userKey.keyGen.signing.recovery.destroyed.revokeCert.reason=0
op.enroll.userKey.keyGen.signing.recovery.destroyed.scheme=GenerateNewKey
Содержание 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 ...