How to Generate Certificate Signing Request (CSR) in IBM HTTP Server running IKEYMAN'

Description

This document provides instructions for generating a Certificate Signing Request (CSR) for IBM HTTP Server running IKEYMAN. If you are unable to use these instructions for your server, RapidSSL recommends that you contact IBM.

NOTE: To generate a CSR, you will need to create a key pair for your server. These two items are a digital certificate key pair and cannot be separated. If you lose your public/private key file or your password and generate a new one, your SSL Certificate will no longer match.

NOTE: All certificates that will expire after October 2013 must have a 2048 bit key size.

Step 1. Create a Key Database File (.kdb)

1.      Open the IKEYMAN Utility 

         On Windows click Start > Programs > IBM HTTP Server > Start Key Management Utility.

         On UNIX  start the iKeyman utility by running: /IHS root/bin/ikeyman.sh

2.      From the Menu Bar select "Key Database File"

3.      Click on NEW

4.      Type in a file name of new Key Database file

5.      Specify the location on the harddrive where the .kdb file will be stored

6.      Click OK


7.      Enter a password

         NOTE: This is the password that will be used to open the .kdb file in IKEYMAN in the future

8.      Make sure to click the box that states "Stash the password to a file?"

         NOTE: This will encrypt the password and save the file as a .sth file in the same directory as the .kdb file. 

9.      Click OK

Step 2. Generate the CSR

1.      Open the Key Database File(.kdb) using the IKEYMAN utility

2.      In the middle of the IKEYMAN GUI, there will be a section called "Key database content"

3.      Click on the "down arrow" to the right, to display a list of three choices

4.      Select "Personal Certificate Requests

5.      From the Personal Certificate Requests section, click New

6.      Fill out the required information:

7.    Key Label is the name used to identify certificate in IKEYMAN

       NOTE: Using the SiteName (for example, www.robo.com) as the label is a good practice.

8.    Key Size must be at least 2048 bits.

       NOTE: If the 2048 bit Key Size does not appear in the drop down list, refer to IBM Support.

- Common Name (CN): The Common Name is the Host + Domain Name. 

NOTE: RapidSSL certificates can only be used on Web servers using the Common Name specified during enrollment. For example, a certificate for the domain "domain.com" will receive a warning if accessing a site named "www.domain.com" or "secure.domain.com", because "www.domain.com" and "secure.domain.com" are different from "domain.com". 

- Organization (O): If your company or department has an &, @, or any other symbol using the shift key in its name, you must spell out the symbol or omit it to enroll, for example: XY & Z Corporation would be XYZ Corportation or XY and Z Corportation.

- Organizational Unit (OU): This field is the name of the department or organization unit making the request.

- Country Name (C): Use the two-letter code without punctuation for country, for example: US or CA.

- Locality or City (L): The Locality field is the city or town name, for example: Berkeley.

- State or Province (S): Spell out the state completely; do not abbreviate the state or province name, for example: California. 

9.      Enter the name of a file in which to store the certificate request

         NOTE: Saving this file(.arm) in the same directory as the (.kdb) file is recommended 

10.    Once the (.arm) file is saved, this completes the CSR generation process

11.    Proceed with Enrolment.

IBM
            For more information refer to IBM documentation
            For more information for creating a key with SHA algorythm, please click here

 

 

Disclaimer:

WarungSSL has made efforts to ensure the accuracy and completeness of the information in this document. However, WarungSSL makes no warranties of any kind (whether express, implied or statutory) with respect to the information contained herein. WarungSSL 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, WarungSSL 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. Geotrust reserves the right to make changes to any information herein without further notice.

Close

We uses cookies to remember and process the items in your shopping cart as well as to compile aggregate data about site traffic and interactions so that we can continue improving your experience on our site.