Updated on 2026-07-15 GMT+08:00

SSL Certificate Usage Process

An SSL certificate (currently standardized as a TLS certificate) is a digital certificate issued by a trusted CA. It is used to verify the identity of a website and encrypt communication between a browser and a server. With an SSL certificate deployed on your web server, the server uses HTTPS to establish encrypted links to the client, ensuring data transmission security. For details about the functions and application scenarios of SSL certificates, see Features, Application Scenarios, and Advantages.

SCM provides certificates of multiple types issued by different CAs. For more details, see Differences Between SSL Certificate Types. This section describes the working principles and usage process of SSL certificates.

Working Principles of an SSL Certificate

HTTPS adds the Secure Sockets Layer (SSL) protocol based on HTTP to encrypt information and data to ensure data transmission security. SSL supports one-way and two-way authentication.

  • One-way authentication: When connecting to a server, a client verifies whether the server is correct.
    One-way SSL authentication applies to the scenario where the client only needs to verify the server identity. For example, in website access, user identity verification is not required at the communication layer, and the application logic layer can ensure security.
    Figure 1 One-way authentication

    1. The client sends information, such as an SSL protocol version, type of encryption algorithm, and random number, to the server.
    2. In addition to an SSL protocol version, type of encryption algorithm, and random number, the server returns a server certificate (public key certificate) to the client.
    3. The client verifies the validity of the server SSL certificate, including whether the server certificate expires, whether the CA of the issued server certificate is reliable, whether the public key of the CA can be used to correctly decrypt the CA digital signature of the server certificate, and whether the domain name in the server certificate matches the server's domain name (that is, the domain name accessed by the user). If the verification is successful, the communication continues. Otherwise, the communication ends.
    4. The client randomly generates a symmetric encryption key, encrypts the key using the server's public key (the server's public key is obtained from the server's certificate in step 2), and sends the encrypted key to the server.
    5. Upon receiving the encrypted information from the client, the server decrypts the information with the private key to obtain the symmetric encryption key.
    6. In the subsequent session, the client and server use the symmetric encryption key to communicate with each other, ensuring information security during the communication.
  • Two-way authentication: When connecting to a server, a client verifies the server and the server also verifies the client.
    The two-way SSL authentication mechanism ensures that the server and client can verify each other's identity, which is mainly used to prevent man-in-the-middle attacks and ensure communication security and reliability. This mechanism is used in scenarios that require high security, such as banks, financial services, IoT, enterprise internal services, and government services, which involve privacy information or provide services only for specific clients.
    Figure 2 Two-way authentication

    1. The client sends information, such as an SSL protocol version, type of encryption algorithm, and random number, to the server.
    2. In addition to an SSL protocol version, type of encryption algorithm, and random number, the server returns a server certificate (public key certificate) to the client.
    3. The client verifies the validity of the server SSL certificate, including whether the server certificate expires, whether the CA of the issued server certificate is reliable, whether the public key of the CA can be used to correctly decrypt the CA digital signature of the server certificate, and whether the domain name in the server certificate matches the server's domain name (that is, the domain name accessed by the user). If the verification is successful, the communication continues. Otherwise, the communication ends.
    4. The server requests the client certificate, and the client sends the certificate and public key to the server.
    5. The server verifies the client certificate. If the verification is successful, the server continues the communication with the client. If the verification fails, the server disconnects from the client.
    6. The client randomly generates a symmetric encryption key, encrypts the key using the server's public key (the server's public key is obtained from the server's certificate in step 2), and sends the encrypted key to the server.
    7. Upon receiving the encrypted information from the client, the server decrypts the information with the private key of the server to obtain the symmetric encryption key.
    8. In the subsequent session, the client and server use the symmetric encryption key to communicate with each other, ensuring information security during the communication.

SSL Certificate Usage Process

Figure 3 and Table 1 show the certificate usage process.
Figure 3 Certificate usage process
Table 1 Certificate usage process

No.

Operation

Description

1

Purchasing an SSL Certificate

On the SCM platform, purchase an SSL certificate for your domain name. For details about how to purchase an official certificate, see Purchasing an Official SSL Certificate. For details about how to create a test certificate, see Creating a Test Certificate. For details about the differences between official and test certificates, see Differences Between SSL Certificate Types.

For more details, see Differences Between SSL Certificate Types and How Do I Select an SSL Certificate?

2

Submitting an SSL Certificate Application to the CA

After you purchase a certificate, associate it with a domain name, provide additional details, and then submit the application to the CA for validation.

Related issues:

How Do I Apply for an Entry-Level SSL Certificate?

3

Verifying Domain Name Ownership

You need to work with the CA to complete the domain name ownership verification.

SCM provides the following domain name ownership verification methods:

Related issues:

How Do I Use DNS to Verify Domains Not Hosted on Huawei Cloud?

4

Verifying the Organization (for OV and EV Certificates)

This operation is required only when you apply for an OV, OV Pro, EV, or EV Pro certificate.

After the domain name ownership is verified, the CA will initiate organization verification.

5

Issuing an SSL Certificate

When the verification is complete, it takes some time for the CA to approve your verification. For details about the application time, see How Long Does It Take for a CA to Approve an SSL Certificate?

The CA will issue the certificate only after they validate your information. An SSL certificate is valid for 200 days from the time it is issued.

6

Installing an SSL Certificate

You can deploy the issued certificate in other Huawei Cloud services in just a few clicks or download the certificate and install it on a server.

  • You can use SCM to quickly deploy SSL certificates to other cloud services to improve their data access security.
  • An SSL certificate cannot enable HTTPS-encrypted communication until it is installed on the web server housing the service.

7

Renewing an SSL Certificate

Since March 15, 2026, global CAs issue only SSL certificates with a maximum validity period of 200 days. When a certificate expires, it will no longer be trusted by the browser. You are advised to enable auto-renewal or manually renew the certificate 30 days before it expires to prevent your services from being affected.

Renewing an SSL certificate is to apply for a new certificate with the exact same configurations as the original one. The configurations include the certificate authority, certificate type, domain type, domain quantity, and primary domain name. After you renew a certificate, install the new certificate on your web server or deploy it on other Huawei Cloud services to replace the old certificate that is about to expire.

8

Revoking an SSL Certificate

If you no longer need an issued SSL certificate for security or other reasons, for example, the certificate key is lost, you can revoke the certificate on the SCM console.

You can revoke a certificate that has been issued by a CA. A revoked certificate is no longer trusted and can no longer be used for certificate-based encryption.

After a certificate is revoked, all its records, including CA records, will be cleared and cannot be restored. Therefore, exercise caution when revoking a certificate.