
Submitting Certificate Requests
215
Figure 10.11. Submitting the Certificate Request
The standard requirements are as follows:
•
Certificate Request Type
. This is either PKCS#10 or CRMF. Certificate requests created
through the subsystem administrative console are PKCS #10; those created through the
certutil
tool and other utilities are usually PKCS #10.
•
Certificate Request
. Paste the base-64 encoded blob, including the
-----BEGIN NEW
CERTIFICATE REQUEST-----
and
-----END NEW CERTIFICATE REQUEST-----
marker
lines.
•
Requester Name
. This is the common name of the person requesting the certificate.
•
Requester Email
. This is the email address of the requester. The agent or CA system
will use this address to contact the requester when the certificate is issued. For example,
.
•
Requester Phone
. This is the contact phone number of the requester.
The submitted request is queued for agent approval. An agent needs to process and approve the
certificate request, which the CA signs then and delivers back to the email address specified in the
request. If the requester has agent access, the requester can log in as an agent and approve the
request.
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 ...