The following instructions will guide you through the CSR generation process on Nginx (OpenSSL). To learn more about CSRs and the importance of your private key, reference our Overview of Certificate Signing Request article. If you already generated the CSR and received your trusted SSL certificate, reference our SSL Installation Instructions and disregard the steps below.
You will want to log in via Secure Shell (SSH).
All SSL Certificates require a private key to work. The private key is a separate file that’s used in the encryption/decryption of data sent between your server and the connecting clients. A private key is created by you—the certificate owner—when you request your certificate with a Certificate Signing. How to generate a certificate signing request and key pair in macOS Keychain Access. Export Certificates and Private Key from a PKCS#12 File with OpenSSL March 3.
Generate a private key and CSR by running the following command:
Here is the plain text version to copy and paste into your terminal:
Note:Replace “server ” with the domain name you intend to secure.
Enter the following CSR details when prompted:
Note: You are not required to enter a password or passphrase. This optional field is for applying additional security to your key pair.
Locate and open the newly created CSR in a text editor such as Notepad and copy all the text including:
Note 1: Your CSR should be saved in the same user directory that you SSH into unless otherwise specified by you.
Note 2: We recommend saving or backing up your newly generate “.key ” file as this will be required later during the installation process.
Return to the Generation Form on our website and paste the entire CSR into the blank text box and continue with completing the generation process.
Upon generating your CSR, your order will enter the validation process with the issuing Certificate Authority (CA) and require the certificate requester to complete some form of validation depending on the certificate purchased. For information regarding the different levels of the validation process and how to satisfy the industry requirements, reference our validation articles. /letasoft-sound-booster-key-generator.html.
After you complete the validation process and receive the trusted SSL Certificate from the issuing Certificate Authority (CA), proceed with the next step using our SSL Installation Instructions for Nginx using OpenSSL.
Before you can install a Secure Socket Layer (SSL) certificate, you must first generate a certificate signing request (CSR). You can do this by using one of the following methods:
The following sections describe how to use OpenSSL to generate a CSR for a single host name. If you want to generate a CSR for multiple host names, we recommend using the Cloud Control Panel or the MyRackspace Portal.
Check whether OpenSSL is installed by using the following command:
CentOS® and Red Hat® Enterprise Linux®
The following output provides an example of what the command returns:
Debian® and the Ubuntu® operating system
The following output provides an example of what the command returns:
If the preceding packages are not returned, install OpenSSL by running the following command:
CentOS and Red Hat
Debian and the Ubuntu operating system
Run the following commands to create a directory in which to store your RSA key, substituting a directory name of your choice:
Run the following command to generate a private key:
Run the following command to create a CSR with the RSA private key (output is in Privacy-Enhanced Mail (PEM) format):
When prompted, enter the necessary information for creating a CSR by using the conventions shown in the following table.
Note: You cannot use the following characters in the Organization Name or Organizational Unit fields: < > ~ ! @ # $ % ^ * / ( ) ? . , &
Field | Explanation | Example |
---|---|---|
Common Name | The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you are purchasing a wildcard certificate, use *.example.com. | example.com |
Organization Name | The exact legal name of your organization. The Certificate Authority (CA) might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name. | Example Inc. |
Organizational Unit | The branch of your organization that is making the request. | Marketing |
City/locality | The city where your organization is legally located. Do not abbreviate the city name. | San Antonio |
State/province | The state or province where your organization is legally located. Do not abbreviate the state or province name. | Texas |
Country/region | The two-letter International Standards Organization (ISO) abbreviation for your country. | US |
Warning: Leave the challenge password blank (press Enter).
Run the following command to verify your CSR:
After you have verified your CSR, you can submit it to a CA to purchase an SSL certificate.
Use the following steps to generate a CSR by using Windows IIS Manager:
Note: The following steps are for IIS 8 or IIS 8.5 on Windows Server 2012.
In the Request Certificate wizard, on the Distinguished Name Properties page, enter the following information and then click Next.
Field | Explanation | Example |
---|---|---|
Common Name | The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you are purchasing a wildcard certificate, use *.example.com. | example.com |
Organization Name | The exact legal name of your organization. The CA might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name. | Example Inc. |
Organizational Unit | The branch of your organization that is making the request. | Marketing |
City/locality | The city where your organization is legally located. Do not abbreviate the city name. | San Antonio |
State/province | The state or province where your organization is legally located. Do not abbreviate the state or province name. | Texas |
Country/region | The two-letter ISO abbreviation for your country. | US |
On the Cryptographic Server Provider Properties page, enter the following information and then click Next.
After you have generated the CSR, you can submit it to a CA to purchase an SSL certificate.
Rackspace provides the CSR Generator for generating a CSR. The CSR Generator shows you the CSRs that you currently have and lets you create new CSRs with a simple form. After you have entered your details, the generator combines them with your private key so that you can submit the combined encoded information to a CA.
When you are done with the generator, you can return to the Cloud Control Panel by clicking any of the links in the top navigation or by going to login.rackspace.com and selecting Rackspace Cloud from the drop-down product menu in the top navigation bar.
Access the CSR Generator directly or through the Control Panel by using the following steps:
/diablo-3-generator-key-download.html. The generator lists your existing CSRs, if you have any, organized by domain name.
Click Create CSR.
Enter the following information, which will be associated with the CSR:
Field | Explanation | Example |
---|---|---|
Domain Name | The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you want to secure both domains, you can use the Alt Names field. If you are purchasing a wildcard certificate, use *.example.com. | example.com |
Alt Names | (Optional) Additional domains that you want to add to the request. Each CA treats these differently, and the CA might charge for additional names. You can submit a comma-separated list. | www.example.com, secure.example.com |
Email Address | (Optional) A contact email address for the certificate. | support@example.com |
Organization Name | The exact legal name of your organization. The CA might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name. | Example Inc. |
Organizational Unit | (Optional) The branch of your organization that is making the request. | Marketing |
City | The city where your organization is legally located. Do not abbreviate the city name. | San Antonio |
State or Province | The state or province where your organization is legally located. Do not abbreviate the state or province name. | Texas |
Country | Choose your country from the drop-down menu. The two-letter ISO abbreviation for your country is included in the CSR. | United States |
Private Key Bit Length | Key sizes smaller than 2048 are considered insecure and might not be accepted by a CA. | 1024,2048,4096 |
Hashing Algorithm | Both algorithms are currently trusted in mainstream browsers and offer industry recommended security. SHA-512 requires additional CPU processing. | SHA-256, SHA-512 |
Note: You cannot use the following characters in the Organization Name or Organizational Unit fields: < > ~ ! @ # $ % ^ * / ( ) ? . , &
After you have entered all the required information, click Create CSR.
It can take between 5 and 60 seconds for the CSR to be generated. You might need to refresh the page that displays your CSRs before the new CSR is listed.
When CSR has been generated, you can click its UUID (unique identifier) in the CSR list to view its details screen.
This screen displays the information that you provided, the text of the CSR, and its associated private key.
The text in the Certificate Request field is the CSR. It contains encoded details of the CSR and your public key.
To request your SSL certificate, copy the Certificate Request text and submit it to your CA. Include all the text, including the BEGIN and END lines at the beginning and end of the text block.
Copy the private key to the server that will host the certificate. See your application documentation to determine where to install the private key and certificate on your server.
If you are a Managed or Dedicated customer, you can request a CSR through the MyRackspace Portal by using the following steps:
Enter the following information in the Ticket Details section:
Field | Explanation | Example |
---|---|---|
Device(s) | The server or servers for which you want to generate a CSR. Use the drop-down menu to select your servers. | |
Common Name | The fully qualified domain name to which the certificate applies. The domain names example.com and www.example.com are distinct from each other, so be sure to submit your request for the right domain. If you want to secure both domains, you can use the Alt Names field. If you are purchasing a wildcard certificate, use *.example.com. | example.com |
Alt. Names | (Optional) Additional domains that you want to add to the request. Each CA treats these differently, and the CA might charge for additional names. You can submit a comma-separated list. | www.example.com, secure.example.com |
Email Address | (Optional) A contact email address for the certificate. | support@example.com |
Organization | The exact legal name of your organization. The CA might seek to confirm that your organization is real and legally registered, so don’t abbreviate words that aren’t abbreviated in the organization’s legal name. | Example Inc. |
Organizational Unit | (Optional) The branch of your organization that is making the request. | Marketing |
Locality (City) | The city where your organization is legally located. Do not abbreviate the city name. | San Antonio |
State or Province Name | The state or province where your organization is legally located. Do not abbreviate the state or province name. | Texas |
Country | Choose your country from the drop-down menu. The two-letter ISO abbreviation for your country is included in the CSR. | United States |
Note: The bit length is automatically set to 2048.
©2020 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License