Extracting a CA certificate from a key repository

Extracting a CA certificate from a key repository

Perform the following steps on the machine from which you want to extract the CA certificate:

Start the iKeyman GUI using either the gsk7ikm command (on UNIX) or the strmqikm command (on Windows).
From the Key Database File menu, click Open. The Open window displays.
Click Key database type and select CMS (Certificate Management System).
Click Browse to navigate to the directory that contains the key database files.
Select the key database file to which you want to add the certificate, for example key.kdb.
Click Open. The Password Prompt window displays.
Type the password you set when you created the key database and click OK. The name of your key database file displays in the File Name field.
In the Key database content field, select Signer Certificates and select the certificate you want to extract.
Click Extract. The Extract a Certificate to a File window displays.
Select the Data type of the certificate, for example Base64-encoded ASCII data for a file with the .arm extension.
Type the certificate file name and location where you want to store the certificate, or click Browse to select the name and location.
Click OK. The certificate is written to the file you specified.

Use the following commands to extract a CA certificate using IKEYCMD or GSKCapiCmd:
On UNIX:
gsk7cmd -cert -extract -db filename -pw password -label label -target filename
        -format ascii
On Windows:
runmqckm -cert -extract -db filename -pw password -label label -target filename
         -format ascii
Using GSKCapiCmd:
gsk7capicmd -cert -extract -db filename -pw password -label label 
            -target filename -format ascii -fips
where:

-db filename is the fully qualified path name of a CMS key database.
-pw password is the password for the CMS key database.
-label label is the label attached to the certificate.
-target filename is the name of the destination file.
-format ascii is the format of the certificate. The value can be ascii for Base64-encoded ASCII or binary for Binary DER data. The default is ascii.
-fips specifies that the command is run in FIPS mode. This mode disables the use of the BSafe cryptographic library. Only the ICC component is used and this component must be successfully initialized in FIPS mode. When in FIPS mode, the ICC component uses algorithms that have been FIPS 140-2 validated. If the ICC component does not initialize in FIPS mode, the gsk7capicmd command fails.

Parent topic:
Transferring certificates

sy12310_

-db filename	is the fully qualified path name of a CMS key database.
-pw password	is the password for the CMS key database.
-label label	is the label attached to the certificate.
-target filename	is the name of the destination file.
-format ascii	is the format of the certificate. The value can be ascii for Base64-encoded ASCII or binary for Binary DER data. The default is ascii.
-fips	specifies that the command is run in FIPS mode. This mode disables the use of the BSafe cryptographic library. Only the ICC component is used and this component must be successfully initialized in FIPS mode. When in FIPS mode, the ICC component uses algorithms that have been FIPS 140-2 validated. If the ICC component does not initialize in FIPS mode, the gsk7capicmd command fails.