Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
- What's New
- Function Overview
- Service Overview
-
SSL Certificate Manager (SCM)
- About SCM and SSL Certificate Usage
- Purchasing an SSL Certificate
- Applying for an SSL Certificate
- Deploying SSL Certificates
-
Managing SSL Certificates
- Reissuing an SSL certificate
- Unsubscribing from an SSL Certificate
- Renewing an SSL Certificate
- Revoking an SSL Certificate
- Deleting an SSL Certificate from CCM
- Uploading an External Certificate to SCM
- Adding an Additional Domain Name
- Withdrawing an SSL Certificate Application
- Canceling Authorization for Privacy Information
- Pushing an SSL Certificate to Other Cloud Services
- Viewing Details About an SSL Certificate
- Viewing the Application Progress
- Permissions Management
- Change History
-
Private Certificate Authority (PCA)
- Overview of Private Certificate Application
- Private CA Management
-
Private Certificate Management
- Applying for a Private Certificate
- Downloading a Private Certificate
-
Installing a Private Certificate
- Trusting a Private Root CA
- Installing a Private Certificate on a Client
-
Installing a Private Certificate on a Server
- Installing a Private Certificate on a Tomcat Server
- Installing a Private Certificate on an Nginx Server
- Installing a Private Certificate on an Apache Server
- Installing a Private Certificate on an IIS Server
- Installing a Private Certificate on a WebLogic Server
- Installing a Private Certificate on a Resin Server
- Revoking a Private Certificate
- Viewing Details of a Private Certificate
- Deleting a Private Certificate
- Permissions Management
- Change History
- API Reference
-
FAQs
-
FAQs
-
Certificate Consulting
- What Are the Differences Between SSL Certificate Manager and Private Certificate Authority?
- Which Websites Require HTTPS?
- What Are the Differences Between HTTPS and HTTP?
- What Is a Public Key and a Private Key?
- What Are the Relationships Between a Public Key, Private Key, and Digital Certificate?
- Why Is a Non-Password-Protected Private Key Required?
- What Are Mainstream Formats of Digital Certificates?
- What Information Does an SSL Certificate Contain?
- Can I Use SSL Certificates for Other Regions, Accounts, or Platforms?
- Can I Use an Unused SSL Certificate Anytime I Want?
- Can SSL Certificates Be Upgraded?
- Does the SSL Certificate Have Restrictions on the Server Port?
- Why Is the Service Displayed as Inaccessible or the Button Displayed in Gray When I Access the SCM Service on the Console?
-
SSL Certificate Application and Purchase
-
SSL Certificate Selection
- Does SCM Provide Free Certificates?
- How Do I Select an SSL Certificate?
- How Can I Apply for a Free SSL Certificate?
- What Can I Do If My Free Certificate Quota Is Used Up?
- How Do I Query the Remaining Quota for Free SSL Certificates?
- How Do I Apply for an Entry-Level SSL Certificate?
- What Are Differences Between Free and Paid SSL Certificates?
- How Do I Apply for a Combination Certificate?
- Can I Change the Certificate Authority, Type, or Bound Domain After A Certificate Is Purchased?
- Problems Related to Certificate Purchases
- How Do I Apply for an SSL Certificate That Uses SM Series Cryptographic Algorithms?
-
About Required Domain Name Details
- How Do I Enter a Domain Name for a Certificate When Applying for an SSL Certificate?
- What Are the Differences Between a Single-Domain Name, Multi-Domain Name, and Wildcard-Domain Name in SCM?
- What Is the Relationship Between a Domain Name and an SSL Certificate?
- What Domains Can Wildcard-Domain Certificates Support?
- What Domain Name Should I Use to Apply for an SSL Certificate?
- Can I Change the Primary Domain Name Associated with a Certificate?
- Does the Relationship Between the Primary Domain Name and Additional Domain Name Have Any Impact on Domain Names?
- How Do I Make a CSR File?
- What Are the Differences Between the CSR Generated by the System and the CSR Made by Yourself?
- Domain-related Concepts
- Problems Related to Domains
-
SSL Certificate Selection
- SSL Certificate Approval
-
SSL Certificate Download, Installation, and Use
-
SSL Certificate Use
- Which Region Will a Certificate Be Deployed to When I Deploy an SSL Certificate in CCM to Other Cloud Product?
- Is HTTPS Automatically Enabled After an SSL Certificate Is Deployed to a Cloud Product?
- Why Is a Message Indicating that the Certificate Chain Is Incomplete Displayed When I Configure HTTPS on CDN?
-
SSL Certificate Use
-
Certificate Validity Period
- What Can I Do If My SSL Certificate Expired?
- How Long Is an SSL Certificate Valid?
- What Can I Do If an SSL Certificate Is About to Expire?
- How Long Does an SSL Certificate Take Effect After Being Purchased?
- Validity Periods and Replacement of the Current and New SSL Certificates
- How Can I Renew an SSL Certificate?
- Will Services Be Affected If an SSL Certificate Is Not Updated After It Expires?
- Validity Periods of Private Certificates
- How Long Will an Order Become Invalid If I Do Not Apply for a Certificate After Purchasing It?
- Certificate Management
-
Certificate Consulting
- Change History
-
FAQs
Show all
Trusting a Private Root CA
Before installing a private certificate, you need to add the root CA to the trusted root certificate authorities of the client or server.
Prerequisites
You have created and exported a private root CA. For details, see Exporting a Private CA Certificate.
Constraints
- One-way authentication
To win more trust from the client for your server, you need to add the root CA that issue the server certificate to the client-end trusted CA store.
- Two-way authentication
To enable two-way authentication between a server and a client, each side needs to add the root CA of the other side to their own trusted root CA store.
Procedure
Use either of the following methods to add the root CA to trusted root certification authorities based on the operating system:
Root CA PCA TEST ROOT G0 is used as an example.
- Windows
- Change the file name extension of the root CA certificate from .pem to .crt. and double-click the certificate file. The root CA certificate information shows that the root certificate is untrusted.
Figure 1 Root CA not trusted
- Click Install Certificate, select a certificate storage location based on the certificate usage, and click Next.
- As shown in Figure 2, select Place all certificates in the following store and click Browse. Then, select Trusted Root Certification Authorities and click OK.
- Click Next, and then click OK. A dialog box is displayed, indicating that Windows will trust all certificates issued by the private root CA. Click Yes.
- Double-click the root CA certificate file. If the Certificate Information area shows that the system trusts the root CA certificate, the root CA is added to the trusted root CAs.
Figure 3 Trusted root CA
- Change the file name extension of the root CA certificate from .pem to .crt. and double-click the certificate file. The root CA certificate information shows that the root certificate is untrusted.
- Linux
The path for and method of storing root CA certificates vary depending on Linux OS versions. The following procedure use CentOS 6 as an example:
- Copy the root CA certificate file to the /home/ directory.
- If ca-certificates is not installed on the server, run the following command to install ca-certificates:
yum install ca-certificates
- Copy the root CA certificate to the /etc/pki/ca-trust/source/anchors/ directory:
cp /home/root.crt /etc/pki/ca-trust/source/anchors/
- Add the root CA certificate to the trusted root certificate file:
- Check whether the information about the newly added root CA certificate is included in the command output:
view /etc/pki/tls/certs/ca-bundle.crt
Figure 4 Root CA certificate added to the trusted CA list
NOTE:
If the OpenSSL version is too old, the configuration may not take effect. You can run the yum update openssl -y command to update the OpenSSL version.
- macOS
- Open the macOS startup console and select Keychain Access.
- Enter the password to log in to Keychain Access.
- Drag and drop the target root CA certificate into Keychain Access. The root CA certificate now is untrusted by the system.
- Right-click the root CA certificate to load its details.
- Click Trust, select Always Trust for When using this certificate, and click Close.
- Enter the password to make the configuration of the trusted root CA certificate take effect.
- View the root CA certificate on the Keychain Access window. If the certificate is trusted by the system, the root CA is successfully added to the trusted root CA store.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.