Certificate Signing Request (CSR) Generation Instructions for BEA Weblogic 8.0, 9.0 and 10.0

Solution ID:    SO22406    Updated:    08/03/2016

Solution


This document was created to assist with the generation of a Certificate Signing Request (CSR) for BEA Weblogic  8.x -10.x. If this document can not be used within the environment, RapidSSL recommends contacting an organization that supports Weblogic.
 
 
Step 1: Create a Keystore and Private Key
 
NOTE: As of 1/1/2016 all public SSL certificates must be issued as SHA-256 with at least a 2048-bit key size.  Please ensure that the server can support these standards before requesting a certificate.
 
  1. Create a keystore and private key by executing the following command.  The private key will be created within the keystore file and labeled with the alias provided in the command.  Please take note of the alias specified, the same alias is required for generating the Certificate Signing Request (CSR) and for the certificate install.

    keytool -genkey -alias [alias name] -keyalg RSA -keystore [keystore filename] -keysize 2048

    For example:

     
  2. Enter and re-enter a keystore password. Tomcat uses a default password of changeit. Hit Enter if you want to keep the default password. If you use a different password, you will need to specify a custom password in the server.xml configuration file.
     
  3. Enter the subject information for the SSL certificate.

    - First and last name / Common Name:  One of these fields will be presented.  Enter the host + domain the certificate will be issued to.  For example:  www.bbtest.net or *.bbtest.net for a wildcard.
    - Organizational Unit (OU): The department or organizational unit making the request.  For example: Technical Support
    - Organization (O): Enter the name of the organization requesting the certificate as it is registered.  Avoid special characters.  For example: Symantec Corporation
    - Locality or City (L): The Locality field is the city or town name, for example: Mountain View.
    - State or Province (S): Spell out the state completely; do not abbreviate the state or province name, for example: California
    - Country Name (C): Use the two-letter code without punctuation for country, for example: US
     
  4. The next step will be to set a private key password.  This will be in addition to the keystore password.

 

Step 2: Generate a Certificate Signing Request (CSR)

  1. Execute the following command to generate the CSR:

    keytool -certreq -keyalg RSA -alias [alias name] -file [CSR file] -keystore [keystore filename]

    For example:


    If an non-current version of Java is used, the command below may be used to specify the SHA-256 algorithm.

    keytool -certreq -keyalg RSA -alias [alias name] -file [CSR file] -keystore [keystore filename] -sigalg SHA256withRSA

    For example:

     
  2. Create a copy of the keystore file. Having a back-up file of the keystore at this point can help resolve installation issues that may occur when importing the certificate.
  3. To copy and paste the full CSR file contents into the enrollment form, open the file in a plain-text editor (Notepad or Vi are recommended).  Below is an example CSR, please be sure to submit the full contents of the CSR including the header and footer lines.
     

    -----BEGIN CERTIFICATE REQUEST-----
    MIIC1jCCAb4CAQAwgZAxCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlh
    MRYwFAYDVQQHDA1Nb3VudGFpbiBWaWV3MR0wGwYDVQQKDBRTeW1hbnRlYyBDb3Jw
    b3JhdGlvbjEgMB4GA1UECwwXV1NTIC0gVGVjaG5pY2FsIFN1cHBvcnQxEzARBgNV
    BAMMCmJidGVzdC5uZXQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDI
    4lm133OQhgoDDHFH6nE0TyfGggoqMag68IIVRcz2DanqYuwMP5EZgko1VHXK35sK
    poF9EEoJp6MC+Pyqefr480BtCGGbB9GtsKUmdkD34aUFugF0DxHFP5sE5vLnYjrd
    yHFwnYSwoo8nzjbkGKEPPIPTmHKs3jseA2ncrOeGUYSTmAlc6NYgH85GVLGeZThY
    qveD97J3wgUAdTcAbWAVDzVqDg4atgwhSlDjIhBtKwxOyt7dJZ/CPII5XHa1DIXq
    10fGk5A4PSlDXgLC2wrDfPeMnmJ5cxXbi7IXdSJx3S5L+0nA2OFz9D7szO5rxOdi
    i8gZm9s118l9kDVBEW4PAgMBAAGgADANBgkqhkiG9w0BAQsFAAOCAQEAFhgnTkv8
    IwqNI32JQzHW+MSWJiqgA7TwopSjH4c2vSmREVtsde4JxfHKPR5GximnFNVdBxK1
    aPYAhW/84hjDaVQ4WLVlrAr6+D5UQy1MH5PBtKM1IQk9fvkxuzBY/Q+fUpBIZE1X
    ypX2XwGUvuO4ymarB+UzA5wYj9Q2PfHE4qqjwFBtsAo73rm2cHa7OpcTq5xR6B31
    M/8rSsIj+cgHvVJacd68sZ9ztJsJ4uxkPyDeKJLKsEe6nLIhyl28VUAX4tG/lsj9
    jDCizT9szxQTjKlMzw/2LBTGpNF02k7TlYAgqLIFOR++zP16zQc5KwY/l3IfNsMj
    DslLwm280Se8yg==
    -----END CERTIFICATE REQUEST-----


     

Once the certificate has been issued, refer to this link for installation instructions.

Legacy ID

vs44181

Disclaimer:

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

Contact Support

US Support:

Order Processing

Technical Support

European Support:

Order Processing

Technical Support

SSL digital certificates sales live chat.

Find Answers


Search Tips