Setting Up The Server For Multiple Requests In A Full Cmc Request; Testing Cmcenroll - Red Hat CERTIFICATE SYSTEM 7.3 - ADMINISTRATION Administration Manual

CMCEnroll -d /certificate/directory -h password
-n cert_nickname -r certrequest.file -p certDB_passwd [-c]
Parameter
d
h
n
r
p
c
Table 16.1. CMCEnroll Usage Options
NOTE
Surround values that include spaces in quotation marks.
16.4.1. Setting up the Server for Multiple Requests in a Full CMC
Request
CMC supports multiple CRMF or PKCS #10 requests in a single full CMC request. If the
numRequests parameter in the .cfg file is larger than 1, modify the server's certificate profile by
doing the following:
1. By default, the servlet processing a full CMC request uses the caFullCMCUserCert profile. This
profile only handles a single request.
2. To use the new profile instead of the default, modify the web.xml file in the /var/lib/rhpki-
ca/webapps/ca/WEB-INF/ directory. Locate the servlet which processes the full CMC request;
by default, this is /ca/profileSubmitCMCFull. Change the value for the profileID
parameter to the name of the new profiles.
For information on creating a new profile, see
3. Restart the server.
/etc/init.d/rhpki-ca restart

16.4.2. Testing CMCEnroll

1. Enable CMCEnroll.

Setting up the Server for Multiple Requests in a Full CMC Request

Description
The location of the directory containing the
cert8.db, key3.db, and secmod.db files
associated with the agent certificate.
Password to the database specified in the d
option.
The common name of the certificate.
The filename of the certificate request.
The password to the browser certificate
database.
Optional. Includes a comment about the
request.
Chapter 13, Certificate Profiles.
385