GeoTrust will email you your certificate. If the certificate is an attachment (Cert.cer), you can use the file. If the certificate is in the body of the email, copy and paste it into a text file (such as OriginalCert.txt) using vi or Notepad. Do not use Microsoft Word or other word processing programs that may add characters.
Confirm that there are no extra lines or spaces in the file.
Installing the certificate
Using the iKeyman graphical user interface (GUI)
After GeoTrust sends you a SSL certificate, you add it to the key database file from which you generated the CSR. If GeoTrust sends you the SSL certificate as part of an email, copy the certificate into a separate file. If necessary, move the file to the server machine.
Start the key management utility (iKeyman). To start the iKeyman graphical user interface:
Windows: go to the start UI and select Start Key Management Utility
AIX, Linux or Solaris: type ikeyman on the command line
- Choose Open from the Key Database File menu. Click Key database type, and select CMS.
- Click Browse to navigate to the directory containing the key database files.
- Select the key database file to which you want to add the certificate. For example, key.kdb.
- Click Open
- In the Password Prompt window, type the password you set when you created the key database and then click OK.
- Select the Personal Certificates view.
- Click Receive
- In the Receive certificate from a file window, select the data type of the new SSL certificate. For example, Base64-encoded ASCII for a file with the .arm extension.
- Click Browse to select the name and location of the certificate file name.
- Click OK
Using the iKeycmd (command line interface)
To install a certificate in iKeycmd (using UNIX command line), use these commands:
gsk7cmd -cert -receive -file filename -db filename -pw password -format ascii
To install a certificate in iKeycmd (using Windows command line), use these commands:
runmqckm -cert -receive -file filename -db filename -pw password -format ascii
Where:
file filename is the fully qualified file name of the file containing the personal certificate.
db filename is the fully qualified file name of a CMS key database.
pw password is the password for the CMS key database.
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.
Transferring certificates
You can extract an SSL certificate from a key database file and store it in a CA key ring file by performing the following steps:
Using the iKeyman graphical user interface (GUI)
- Start the iKeyman graphical user interface (GUI) using either the gsk7ikm command (UNIX) or the strmqikm command (Windows).
- Choose Open from the Key Database File menu. Click Key database type, and select CMS.
- Click Browse to navigate to the directory containing the key database files
- Select the key database file to which you want to add the certificate. For example, key.kdb.
- Click Open
- In the Password Prompt window, type the password you set when you created the key database and then click OK.
- Select Signer Certificates in the Key database content field, and then select the certificate you want to extract.
- Click Extract.
- Select the Data type of the certificate. For example, Base64-encoded ASCII data for a file with the .arm extension
- Click Browse to select the name and location of the certificate file name.
- Click OK. The certificate is written to the file you specified.
Using the iKeycmd (command line interface)
To extract a certificate in iKeycmd (using UNIX command line), use these commands:
gsk7cmd -cert -extract -db filename -pw password -label label -target filename -format ascii
To extract a certificate in iKeycmd (using Windows command line), use these commands:
runmqckm -cert -extract -db filename -pw i -label label -target filename -format ascii
Where:
db filename is the fully qualified pathname of a 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
Disclaimer:
Firehost has made efforts to ensure the accuracy and completeness of the information in this document. However, Firehost makes no warranties of any kind (whether express, implied or statutory) with respect to the information contained herein. Firehost assumes no liability to any party for any loss or damage (whether direct or indirect) caused by any errors, omissions, or statements of any kind contained in this document.
Further, Firehost assumes no liability arising from the application or use of the product or service described herein and specifically disclaims any representation that the products or services described herein do not infringe upon any existing or future intellectual property rights. Nothing herein grants the reader any license to make, use, or sell equipment or products constructed in accordance with this document. Finally, all rights and privileges related to any intellectual property right described herein are vested in the patent, trademark, or service mark owner, and no other person may exercise such rights without express permission, authority, or license secured from the patent, trademark, or service mark owner. Firehost reserves the right to make changes to any information herein without further notice.