Certificate Signing Request (CSR) Generation Instructions for IBM WebSphere MQ using the IKEYMAN GUI

Solution ID:    SO15219    Updated:    06/14/2017

Solution

This document provides instructions for generating a Certificate Signing Request (CSR) for IMB Websphere MQ using IKEYMAN GUI. If you are unable to use these instructions for your server, Symantec recommends that you contact IBM.
 
NOTE: Before generating a CSR, you first 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, forget your password, or generate a new key file, your SSL Certificate will no longer match your private key. You will have to replace the SSL Certificate and may be charged.

For more information about selecting  signature algorithm in ikeyman please refer to the IBM website

NOTE: To generate a CSR using the command line, follow the steps from this link.

Step 1. Create a Keystore using iKeyman utility

  1. Start the iKeyman GUI using either the gsk7ikm command (UNIX) or the strmqikm command (Windows) 
    NOTE: To use the iKeyman GUI, be sure that your machine can run the X Windows system
  2. Open WebSphere MQ Explorer and right-clicking on IBM Websphere MQ
  3. Select Manage SSL Certificates.
  4. The tool displays a graphical interface that looks like


     
  5. Create the key database file by selecting Key Database File > New.


     
  6. Accept the default key database type of CMS.
  7. Use the default location for the key database, which is <mqroot>\Qmgrs\<qmgrname>\ssl. The default name is key.kdb


     
  8. Enter a Location for the location on the hard drive where you want to store the .kdb file.
    NOTE:  The default location is: C:\Program Files\IBM\WebSphere\AppServer\profiles\default\etc,
    but you also can provide a different location where you want to store your keystore file. 


     
  9. Click OK.
  10. Enter a password and click OK.
     

Step 2.  Generate a Certificate Signing Request

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

  1. From the iKeyman graphical user interface (GUI) click Create
  2. Click New Certificate Request
  3. Type the following in the Key Label field: For a WebSphere MQ client, ibmwebspheremq followed by your logon user ID (in lowercase).
    For example:
    ibmwebspheremqmyuserid.
  4. The 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 one of the following IBM solutions : Solution 1/ Solution 2
  5. The CSR needs to contain the following attributes :
     
    • Country Name (C): Use the two-letter code without punctuation for country, for example: US or CA.
    • State or Province (S): Spell out the state completely; do not abbreviate the state or province name, for example: California.
    • Locality or City (L): The Locality field is the city or town name, for example: Berkeley.
    • 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.
    • Organizational Unit (OU): This field is the name of the department or organization unit making the request.
    • Common Name (CN): The Common Name is the Host + Domain Name. It looks like "www.symantec.com" or "symantec.com".
       
  1. For Enter the name of a file in which to store the certificate request, either accept the default certreq.arm, or type a new path name.
  2. Click OK. When the confirmation window displays, click OK again.
  3. The file you created contains the CSR
  4. Verify your CSR
  5. Proceed with Enrollment 
     

Contact Information

         During the verification process, Symantec may need to contact your organization. Be sure to provide an email address, 
         phone number and fax number that will be checked and responded to quickly. These fields are not part of the certificate.
 

Once the SSL certificate has been issued, follow the steps from this link to install it on the server.

IBM

        For more information refer to IBM documentation
 
 

Disclaimer:

Terms of use for this information are found in Legal Notices

Contact Support

Find Answers