Before a Certificate Authority can issue your SSL certificate, you need to generate a CSR (Certificate Signing Request) on the server where the certificate will be installed. The CSR carries your public key and domain details. You send us the CSR. The private key never leaves your server.
Whichever server you use, the steps to generate a CSR for an SSL certificate ask for the same details. Have them ready before you start. For OV and EV certificates, the organisation details must match your company registration.
www.example.com*.example.com.Example Company (Pty) LtdIT Web SecurityJohannesburgGautengZA, ZW, CDDigiCert requires a key size of at least 2048 bits. A CSR with a smaller key will be rejected.
Securing several different hostnames on one certificate? The extra names are added as Subject Alternative Names (SANs), normally during the order rather than in the CSR itself. Give us the full list when you order.
Pick the platform where the certificate will be installed and generate the CSR on that same server. The SSL certificate we issue will only work with the private key created alongside your CSR.
-----BEGIN NEW CERTIFICATE REQUEST----- ... -----END NEW CERTIFICATE REQUEST-----
https://localhost/ecp
\\SERVER\Share\mail-example-com.csr
openssl req -new -newkey rsa:2048 -nodes \ -keyout example.com.key \ -out example.com.csr
# Example answers
Country Name (2 letter code): ZA
State or Province Name: Gauteng
Locality Name: Johannesburg
Organization Name: Example Company (Pty) Ltd
Organizational Unit Name: IT
Common Name: www.example.comopenssl req -new -newkey rsa:2048 -nodes \ -keyout example.com.key -out example.com.csr \ -subj "/C=ZA/ST=Gauteng/L=Johannesburg/O=Example Company (Pty) Ltd/OU=IT/CN=www.example.com"
openssl req -noout -text -in example.com.csr
cat example.com.csr
openssl req -new -newkey rsa:2048 -nodes \ -keyout server.key \ -out server.csr
chmod 600 server.key
keytool -genkeypair -alias server \ -keyalg RSA -keysize 2048 \ -keystore example.com.jks
keytool -certreq -alias server \ -file csr.txt \ -keystore example.com.jks
Paste the CSR you generated to decode it and confirm the details are correct. The checker verifies the signature, key size, hash algorithm, Common Name, country code and Subject Alternative Names, and tells you what to fix before you order your SSL certificate.
The private key and the CSR are a matched pair. The SSL certificate issued from your CSR will only install against the private key created with it.
| example.com.csr | ||
| example.com.key / .jks | ||
Only the CSR is sent to Prima Secure or the certificate authority. If the key is lost, you will need to generate a new CSR and have the certificate reissued.
www.example.com for a standard certificate, *.example.com for a wildcard, mail.example.com for mail services.
Create it on the machine where the SSL certificate will be installed, or plan to move the private key securely.
Smaller keys are rejected. 2048 bits is the minimum; 3072 or 4096 are also accepted.
Include the BEGIN and END lines, with no extra spaces or missing characters. A truncated CSR cannot be processed.
For multi-domain certificates, give us all the SANs when you order so the certificate covers everything first time.
Based on DigiCert’s CSR guidance. For other platforms, see the DigiCert CSR knowledge base.
A Certificate Signing Request (CSR) is an encoded block of text generated on your server. It contains your public key and the details of the domain and organisation the SSL certificate will cover. The Certificate Authority uses it to create your certificate.
Generate the CSR on the server where the SSL certificate will be installed, such as your IIS, Exchange, Apache, Ubuntu or Tomcat server. That server keeps the matching private key needed for installation.
Paste it into the CSR checker on this page. It decodes the CSR in your browser and checks the signature, key size, hash algorithm, Common Name, country code and Subject Alternative Names. Nothing is uploaded.
No. You only send the CSR. Never share your private key with Prima Secure, the Certificate Authority or anyone else.
Use RSA with a key size of at least 2048 bits, or an ECC P-256 or P-384 key. DigiCert rejects RSA keys smaller than 2048 bits.
Follow the same steps for your server, but enter the Common Name in wildcard format, for example *.example.com.
It is possible on some platforms, but we recommend you generate a new CSR and private key at each renewal. Fresh keys limit the impact if an old key was ever exposed.
Buy your SSL certificate, paste the full CSR into the order, and complete validation. Once the certificate is issued, install it on the same server together with the intermediate certificate.
Prima Secure is one of Africa’s largest DigiCert and Sectigo resellers. Choose your SSL certificate, paste in your CSR, and our team will support you through validation and installation. Questions? Email sales@primasecure.com.