Terms Used for SCM
This topic describes some terms related to Huawei Cloud SSL Certificate Manager (SCM).
Digital Certificate
A digital certificate is a file digitally signed by a CA and contains information about the owner of a public key and the public key. It is a trusted certificate issued by an authority to a website. The simplest certificate contains a public key, name, and digital signature of the CA. Another important feature of a digital certificate is that it is valid only within a specific period of time.
SSL Protocol
SSL is an encryption protocol that secures communication over a computer network. It establishes an encrypted channel between the browser and website to prevent information from being stolen or tampered with during transmission.
Certificate Authority
A Certificate Authority (CA) is an authority responsible for issuing and managing digital certificates. As a trusted third party in e-commerce transactions, the CA verifies the validity of public keys in the public key system.
HTTPS
Hypertext Transfer Protocol Secure (HTTPS) is a website encryption transmission protocol based on the SSL protocol. HTTPS activates an SSL encrypted channel between a web browser and a website server for a user to visit the website where an SSL certificate has been installed. The channel enables high-strength bidirectional encrypted transmission to prevent leakage or tampering of the data in transit. HTTPS is the secure version of HTTP.
CSR
A certificate signing request (CSR) is a message sent from an applicant to a CA to apply for an SSL certificate. A CSR file contains a public key and a distinguished name (DN). Typically, a CSR file is generated by a web server, and a pair of public and private keys are created along with the CSR file.
SSL Certificate Validity Period
From September 1, 2020, only one-year SSL certificates can be issued by CAs around the world. Therefore, the validity period of an SSL certificate you apply for through Huawei Cloud CCM is one year.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
