What is a CSR? A CSR or Certificate Signing request is a block of encoded text that is given to a Certificate Authority when applying for an SSL Certificate. It is usually generated on the server where the certificate will be installed and contains information that will be included in the certificate such as the organization name, common name (domain name), locality, and country. It also contains the public key that will be included in the certificate. A private key is usually created at the same time that you create the CSR, making a key pair. A CSR is generally encoded using ASN.1 according to the PKCS #10 specification.
A certificate authority will use a CSR to create your SSL certificate, but it does not need your private key. You need to keep your private key secret. The certificate created with a particular CSR will only work with the private key that was generated with it. So if you lose the private key, the certificate will no longer work.
However, only the Certificates MMC comes installed by default on Microsoft Windows clients and servers. It can be a little finicky at first, but once you understand the underpinnings of the utility, it is an excellent tool. Use these instructions to generate a Certificate Signing Request (CSR) in Microsoft Management Console (MMC).
Name | Explanation | Examples |
---|---|---|
Common Name | The fully qualified domain name (FQDN) of your server. This must match exactly what you type in your web browser or you will receive a name mismatch error. | *.google.com |
Organization | The legal name of your organization. This should not be abbreviated and should include suffixes such as Inc, Corp, or LLC. | Google Inc. |
Organizational Unit | The division of your organization handling the certificate. | Information Technology IT Department |
City/Locality | The city where your organization is located. | Mountain View |
State/County/Region | The state/region where your organization is located. This shouldn't be abbreviated. | California |
Country | The two-letter ISO code for the country where your organization is location. | US GB |
Email address | An email address used to contact your organization. | [email protected] |
Public Key | The public key that will go into the certificate. | The public key is created automatically |
Most CSRs are created in the Base-64 encoded PEM format. This format includes the '-----BEGIN CERTIFICATE REQUEST-----' and '-----END CERTIFICATE REQUEST-----' lines at the begining and end of the CSR. A PEM format CSR can be opened in a text editor and looks like the following example:
-----BEGIN CERTIFICATE REQUEST-----
MIIByjCCATMCAQAwgYkxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlh
MRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRMwEQYDVQQKEwpHb29nbGUgSW5jMR8w
HQYDVQQLExZJbmZvcm1hdGlvbiBUZWNobm9sb2d5MRcwFQYDVQQDEw53d3cuZ29v
Z2xlLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEApZtYJCHJ4VpVXHfV
IlstQTlO4qC03hjX+ZkPyvdYd1Q4+qbAeTwXmCUKYHThVRd5aXSqlPzyIBwieMZr
WFlRQddZ1IzXAlVRDWwAo60KecqeAXnnUK+5fXoTI/UgWshre8tJ+x/TMHaQKR/J
cIWPhqaQhsJuzZbvAdGA80BLxdMCAwEAAaAAMA0GCSqGSIb3DQEBBQUAA4GBAIhl
4PvFq+e7ipARgI5ZM+GZx6mpCz44DTo0JkwfRDf+BtrsaC0q68eTf2XhYOsq4fkH
Q0uA0aVog3f5iJxCa3Hp5gxbJQ6zV6kJ0TEsuaaOhEko9sdpCoPOnRBm2i/XRD2D
6iNh8f8z0ShGsFqjDgFHyF3o+lUyj+UC6H1QW7bn
-----END CERTIFICATE REQUEST-----
You need to generate a CSR and private key on the server that the certificate will be used on. You can find instructions in your server documentation or try the instructions from one of these certificate authorities:
Comodo CSR Generation Instructions
DigiCert CSR Generation Instructions
Entrust CSR Generation Instructions
GeoTrust CSR Generation Instructions
Thawte CSR Generation Instructions
Once you have your CSR generated, you can use our SSL Wizard to find the best SSL certificate that will meet your needs. If you are familiar with OpenSSL you can use the following command to generate a CSR and private key:
openssl req -new -newkey rsa:2048 -nodes -out servername.csr -keyout servername.key
You can easily decode your CSR to see what is in it by using our CSR Decoder. In order to decode a CSR on your own machine using OpenSSL, use the following command:
openssl req -in server.csr -noout -text
The bit-length of a CSR and private key pair determine how easily the key can be cracked using brute force methods. As of 2016, a key size of less than 2048 bits is considered weak and could potentially be broken in a few months or less with enough computing power. If a private key is broken, all the connections initiated with it would be exposed to whomever had the key. The Extended Validation guidelines that SSL certificate providers are required to follow, require that all EV certificates use a 2048-bit key size to ensure their security well into the future. Because of this, most providers encourage 2048-bit keys on all certificates whether they are EV or not.
Originally posted on Sun Dec 7, 2008
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:
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. | [email protected] |
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: < > ~ ! @ # $ % ^ * / ( ) ? . , &
Indigo renderer licence key generator. Even for the new users it takes little time to get set with application.
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. | [email protected] |
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