Through a series of screenshots below, I’ll show you my configuration. It allows you to get a really good feel for what’s happening under the covers without writing a bunch of code. You can leverage any MQTT 3.1.1 client to talk to DPS, however, like in previous articles, I’m going to use MQTT.fx, which is an excellent MQTT GUI tool for ‘manually’ doing MQTT.
We will call that the “DPS-root-CA” cert. The easiest way to get this cert, is to open this file from the Azure IoT C SDK, copy everything from (and including) line 23 to (and including) line 43, then strip out the quotes at the beginning and end of each line, and strip off the ‘\r\n’ off the ends. The client needs this to validate that it is indeed talking to the genuine microsoft endpoint and not a ‘man in the middle’. This is the Baltimore-based root ca cert from which all the IoT Hub and DPS “server-side” TLS certificates are generated. The only other thing you need is the IoT Root CA cert.
Kepserverex receive data mqttclient registration#
Specifically the sections titled “Prep work (aka – how do I generate test certs?)” and “X.509 attestion with individual enrollments- setup”, so I won’t repeat them here… For the screenshots below, I called my enrollment registration id ‘dpstestdev01’. The steps for generating the device certificates and creating the enrollment in DPS is the same process as outlined in my DPS over REST API article. The process was nearly identical except for a few fields in the connection information, specifically specifying the iothub root cert, the device cert/key, and leaving off the SAS token. Based on the knowledge from the previous article, as well as my article on DPS over the REST APIs, it was pretty straightforward. Since it’s inevitable that I’ll run across this in a customer situation, I thought I’d tackle it.
the SAS-token based authentication that the article was based on. A reader/commenter asked how the process would differ if we used x.509 certificate based authentication vs.
Kepserverex receive data mqttclient how to#
In a previous post, I showed you how to register a device with Azure’s Device Provisioning Server (DPS) over raw MQTT.
0 kommentar(er)
