이 콘텐츠는 선택한 언어로 제공되지 않습니다.
16.2. Usage
CRMFPopClient
has two different methods of handling the requests it generates: it can send it directly to a CA or it can simply print the request to stdout.
Important
A file named
transport.txt
containing the transport certificate in base-64 format must be created in the directory from which the utility is launched. This file must be available for archival to a KRA. If the file is present, then the tool picks up this file automatically and performs the key archival.
The
transport.txt
must have the entire base 64-encoded transport certificate on a single line with the header and footer removed.
Sending a request to a CA
The following example generates a CRMF/POP request, has the server verify that the information is correct, and prints the certificate request to the screen:
CRMFPopClient secret caUserCert host.example.com 1026 CaUser jsmith POP_SUCCESS CN=MyTest,C=US,UID=CaUser
CRMFPopClient secret caUserCert host.example.com 1026 CaUser jsmith POP_SUCCESS CN=MyTest,C=US,UID=CaUser
Printing the request to stdout
A request can simply be printed to stdout. This can be useful if the certificate request is going to be submitted to an external CA or directly through the CA's web services pages. Processing the request, in this case, requires additional manual steps:
- Use
CRMFPopClient
to generate the request, encoded with POP data.CRMFPopClient secret POP_SUCCESS OUTPUT_CERT_REQ CN=MyTest,C=US,UID=CaUser
CRMFPopClient secret POP_SUCCESS OUTPUT_CERT_REQ CN=MyTest,C=US,UID=CaUser
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Copy the request that is printed to the screen.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Open the CA's end-entities pages.
https://server.example.com:9444/ca/ee/ca/
https://server.example.com:9444/ca/ee/ca/
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Submit the request to any profile which supports CRMF/POP requests.