3. Obtain the content of the certificate request file and visit CA sites to apply for a certificate.
Certificate Format Requirements
The certificate that needs to be applied for should be in PEM format on Linux. CLB does not support certificates in other formats. For more information, see Converting Certificates to PEM format.
If your certificate is issued by a root CA, the certificate is unique, and the configured website will be considered trustworthy by browsers and other accessing devices with no additional certificates required.
If your certificate is issued by an intermediate CA, your certificate file will consist of multiple certificates. In this case, you need to manually combine the server certificate and intermediate certificate for upload.
If your certificate has a certificate chain, please convert it to PEM format and merge with the certificate content for upload.
The concatenation rule is as follows: put the server certificate before the intermediate certificate with no blank lines in between.
Note:
You can check for applicable rules or instructions provided by the CA when issuing the certificate.
Certificate format and certificate chain format
Below are examples of certificate and certificate chain formats. Please confirm the format before upload:
1. Certificate issued by a root CA: PEM format on Linux, as shown below:
Certificate rules are:
Your certificate should start with "——-BEGIN CERTIFICATE——-" and end with "——-END CERTIFICATE——-", which should be uploaded together.
Each line should contain 64 characters, while the last line can contain less than 64 characters.
2. Certificate chain from an intermediate CA:
——-BEGIN CERTIFICATE——-
——-END CERTIFICATE——-
——-BEGIN CERTIFICATE——-
——-END CERTIFICATE——-
——-BEGIN CERTIFICATE——-
——-END CERTIFICATE——-
Certificate chain rules:
No blank lines between certificates.
All certificates should meet the requirements as above.
RSA Private Key Format Requirements
Below is an example:
RSA private key can include all private keys (RSA and DSA), public keys (RSA and DSA), and (X.509) certificates. It stores data in Base64-encoded DER format and is wrapped by ASCII headers, making it suitable for transmission in text mode between systems.
RSA private key rules:
Your certificate should start with "——-BEGIN RSA PRIVATE KEY——-" and end with "——-END RSA PRIVATE KEY——-", which should be uploaded together.
Each line should contain 64 characters, while the last line can contain less than 64 characters.
If your private key does not start with "——-BEGIN PRIVATE KEY——-" and end with "——-END PRIVATE KEY——-", you can convert it in the following way:
You can then upload new_server_key.pem content together with the certificate.
Converting Certificates to PEM Format
Currently, CLB only supports certificates in PEM format. Certificates in other formats need to be converted to PEM format first before uploading to CLB. We recommend you use OpenSSL. The following shows how to convert several common formats to PEM.
DER to PEM
P7B to PEM
PFX to PEM
CER/CRT to PEM
DER format is generally used on Java platforms.
Certificate conversion:
openssl x509 -inform der -in certificate.cer -out certificate.pem
Private key conversion:
openssl rsa -inform DER -outform PEM -in privatekey.der -out privatekey.pem
P7B format is generally used on Windows Server and Tomcat.
Certificate conversion:
You need to get the content between "——-BEGIN CERTIFICATE——-" and "——-END CERTIFICATE——-" in outcertificat.cer to upload as certificate.
Private key conversion: private keys can generally be exported on IIS servers.
PFX format is generally used on Windows Server.
Certificate conversion:
You can convert certificates in CER/CRT formats to PEM by directly modifying their file extension names. For example, you can directly rename the servertest.crt certificate file as servertest.pem.
