
Publishing Cross-Pair Certificates
323
If the Directory Server is configured for SSL communication with client authentication, select
SSL client authentication
and the
Use SSL communication
option, and identify the
certificate that the Certificate Manager must use for SSL client authentication to the directory.
The server attempts to connect to the Directory Server. If the information is incorrect, the server
displays an error message.
14.6.1. Publishing Cross-Pair Certificates
The cross-pair certificates can be published as a
crossCertificatePair
entry to an LDAP
directory or to a file; this is enabled by default. If this has been disabled, it can be reenabled through
the Certificate Manager Console by doing the following:
1. Open the CA Console
pkiconsole https://server.example.com:9443/ca
2. In the
Configuration
tab, select the
Certificate Manager
link in the left pane, then the
Publishing
link.
3. Click the
Rules
link under
Publishing
. This opens the
Rules Management
pane on the right.
4. If the rule exists and has been disabled, select the
enable
checkbox. If the rule has been deleted,
then click
Add
and create a new rule.
a. Select
xcerts
from the
type
drop-down menu.
b. Make sure the
enable
checkbox is selected.
c. Select
LdapCaCertMap
from the
mapper
drop-down menu.
d. Select
LdapCrossCertPairPublisher
from the
publisher
drop-down menu.
The mapper and publisher specified in the publishing rule are both listed under
Mapper
and
Publisher
under the
Publishing
link in the left navigation window of the CA Console. The mapper,
LdapCaCertMap
, by default designates that the
crossCertificatePair
be stored to the
LdapCaSimpleMap
LDAP entry. The publisher,
LDAPCrossPairPublisher
, by default sets the
attribute to store the cross-pair certificate in the CA entry to
crossCertificatePair;binary
.
14.7. Testing Publishing to Files
To verify that the Certificate Manager is publishing certificates and CRLs correctly to file, do the
following:
1. Open the CA's end-entities page, and request a certificate.
2. Approve the request through the agent services page, if required.
3. Retrieve the certificate from the end-entities page, and download the certificate into the browser.
4. Check whether the server generated the DER-encoded file containing the certificate.
Summary of Contents for CERTIFICATE SYSTEM 7.2 - MIGRATION GUIDE
Page 36: ...Chapter 1 Overview 16 Figure 1 4 Certificate System Architecture ...
Page 144: ...124 ...
Page 160: ...140 ...
Page 208: ...188 ...
Page 210: ...190 ...
Page 256: ...236 ...
Page 282: ...Chapter 12 Certificate Profiles 262 Parameter IssuerName_n IssuerType_n ...
Page 285: ...Freshest CRL Extension Default 265 Parameter PointName_n PointIssuerName_n ...
Page 362: ...342 ...
Page 376: ...356 ...
Page 436: ...416 ...
Page 490: ...470 ...
Page 504: ...484 ...