Chapter 2. Making Rules for Issuing Certificates
54
2.4.1. Editing Enrollment Profiles for the TPS
Administrators have the ability to customize the default smart card enrollment profiles, used with
the TPS. 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:
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
.
Editing certificate profiles is covered in
Section 2.2, “Setting up Certificate Profiles”
.
2.4.2. Creating Custom TPS Profiles
Certificate profiles are created as normal in the CA, but they also have to be configured in the TPS for
it to be available for token enrollments.
TIP
New profiles are added with new released of Red Hat Certificate System. If an instance is
migrated to Certificate System 8.0, then the new profiles need to be added to the migrated
instance as if they are custom profiles.
1. Create a new token profile for the issuing CA. Setting up profiles is covered in
Section 2.2, “Setting
up Certificate Profiles”
.
2. Copy the profile into the CA's profiles directory,
/var/lib/
subsystem_name
/profiles/ca
.
3. Edit the CA
CS.cfg
file, and add the new profile references and the profile name to the CA's list of
profiles. For example:
vim /etc/
subsystem_name
/CS.cfg
profile.list=caUserCert,...,caManualRenewal,
tpsExampleEnrollProfile
...
profile.caTokenMSLoginEnrollment.class_id=caUserCertEnrollImpl
profile.caTokenMSLoginEnrollment.config=/var/lib/
subsystem_name
/profiles/ca/
tpsExampleEnrollProfile.cfg
4. Edit the TPS
CS.cfg
file, and add a line to point to the new CA enrollment profile. For example:
vim /etc/pki-tps/CS.cfg
Summary of Contents for CERTIFICATE SYSTEM 8.0 - ADMINISTRATION
Page 42: ...20 ...
Page 43: ...Part I Setting up Certificate Services ...
Page 44: ......
Page 190: ...168 ...
Page 208: ...186 ...
Page 223: ...Part II Additional Configuration to Manage CA Services ...
Page 224: ......
Page 256: ...234 ...
Page 270: ...248 ...
Page 280: ...258 ...
Page 292: ...270 ...
Page 293: ...Part III Managing the Subsystem Instances ...
Page 294: ......
Page 408: ...386 ...
Page 438: ...416 ...
Page 439: ...Part IV References ...
Page 440: ......
Page 503: ...Netscape Defined Certificate Extensions Reference 481 OID 2 16 840 1 113730 13 ...
Page 504: ...482 ...
Page 556: ...534 ...
Page 564: ...542 ...