Help Center>
IoT Device Management>
FAQs>
Secondary Development>
FAQs About Application Development>
Subscription and Push>
How Do I Export the HTTPS Push Certificate
Updated on 2022-02-24 GMT+08:00
How Do I Export the HTTPS Push Certificate
- Start a browser, and type the callback address in the address box. Internet Explorer is used as an example.
- Check the certificate. The methods for checking a self-signed certificate and non-self-signed certificate are different.
- If the callback address uses a self-signed certificate, the message "There is a problem with this website's security certificate" is displayed. Choose Figure 1 Self-signed certificate callback address prompt
Figure 2 Checking the self-signed certificate
.
- If the callback address is not a self-signed certificate, choose Figure 3 Checking the non-self-signed certificate
.
- If the callback address uses a self-signed certificate, the message "There is a problem with this website's security certificate" is displayed. Choose
- Check the certificate level on the Certification Path tab page. The current certificate level is the last level of the certificate.
Figure 4 Certificate path
Figure 5 Common certificate information
- On the Details tab page, click Copy to File, and select Base-64 encoded X.509 (.CER) to export the certificate of the current level based on the certificate export wizard.
Figure 6 Detailed certificate information
Figure 7 Selecting the certificate export format
- Double-click the upper-level certificate. In the displayed dialog box, choose to export the upper-layer certificate by following instructions provided by the certificate export wizard.
- Repeat 5 until all levels of certificates are exported.
- Use the text editor to combine all the exported certificates into a file.
NOTE:
No newline character exists between the combined files.
Figure 8 Combining certificates
- Change the file name suffix to pem.
- On the Developer Center, choose
to upload the certificate to the IoT platform.Figure 9 Uploading the certificate
Parent topic: Subscription and Push
Subscription and Push FAQs
- Invalid Callback Address Occurs When Calling the Subscription API
- How to Obtain the subscriptionId When Calling the Querying Subscription in Batches API
- Application Server Fails to Receive Data Pushed by the IoT Platform
- How Do I Export the HTTPS Push Certificate
- Difference Between deviceDatachanged and deviceDataschanged
- How Does an Application Server Obtain the IMEI of Devices
- Application Server Receives Data But an Error Is Displayed on the IoT Platform
- Push Messages May Fail to Be Sent to Application Servers
- How Does an Application Servers Obtain The Address Used by the IoT Platform to Push Messages
- Does the IoT Platform Supports Re-push
- How Does an Application Server Receive a Command Status Change Notification
- Application Servers That Have Subscribed to Confirmation Notifications and Command Response Notifications Fail to Receive Push Messages
- Does the IoT Platform Support Only HTTPS Callback Addresses
- Can the IoT Platform Push Data Reported by Different Devices Under the Same Application to Two Servers
- Can a Subscription Address Be a Domain Name
- Can a Callback Address Be Changed
- How Do I Obtain the Callback URL When Calling the Subscription API
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore