Hello everyone,
I guess, if I am not mistaken, that XDK cannot authenticate itself on a MQTT broker with a certificate if we are developing in MITA or in C. Because I would like to add security steps on the authentication of the device, because the login and password are always detectable in the source code and are not reliable ways to authentication nowadays.
So, my question is, to prevent, for example "man in the middle" between devices, and strengthen the security, could XDK device use its own client certificate for authentication ? I would like to use it into MQTTS discussion. The broker that I use (Eclipse Mosquitto) already support client's certificates authentication. I will be pleased to try this functionality.
Regards,
Hello everyone,
I guess, if I am not mistaken, that XDK cannot authenticate itself on a MQTT broker with a certificate if we are developing in MITA or in C. Because I would like to add security steps on the authentication of the device, because the login and password are always detectable in the source code and are not reliable ways to authentication nowadays.
So, my question is, to prevent, for example "man in the middle" between devices, and strengthen the security, could XDK device use its own client certificate for authentication ? I would like to use it into MQTTS discussion. The broker that I use (Eclipse Mosquitto) already support client's certificates authentication. I will be pleased to try this functionality.
Regards,