This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL-CC3235SF: SS

Part Number: LAUNCHXL-CC3235SF



Hi Ti Expert,

is there any documents and lib for self-signed cert for MQTTs client connections?

in the MQTTs connections require to attach certificates files for connections. if certificates are not attach then client can not connection establish.

I want know that i am not attach certificates file and when the API call for the connection establish and lib auto generate the certificates files and attached the API.

When you open "ti.com"on chrome web browser.
ti.com is working on secure web socket and you can access from chrome browser without any certificates file. In this process chrome have self-signed certificates policy, certificate generate and attach with chrome for temp and access that website. same thing happen in the MQTTs client connection establish.



Best Regards,
D J

  • Hi D J,

    No. It seems you not understand haw certificates (asymmetric cryptography) works. Chrome does not generate any self-signed certificate for https connection. HTTPs (TLS) connection itself does not need any certificate. But certificates are used to validate opposite partner (protection against man-in-the middle attack). For this purpose chrome incorporate root certificates for validation of certificate chain.

    Brief introduction about certificates at CC32xx you find here.

    Jan

  • Hi Jan,

    I understood one public certificate are require to connect the MQTTs server.

    source :- SimpleLinkTm WiFi Certificates Handling (Rev. A) (Section 2.5.5)


    Chrome have already to placed public certificate file in install folder.
    (It automatically take it from the server and placed it, while chrome was newly install).


    Thanks for the support.

    Best Regards,
    D J