Each of the device instance need to have it's own cert. However, when using group enrollment, they would all derive from the same root CA cert. See details in here: docs.microsoft.com/en-us/azure/iot-dps/concepts-security#attestation-mechanism
The devices are connecting to the Device Provisioning Service in order to be provisioned automatically to the right instance of IoT Hub. You can find details in the docs here: docs.microsoft.com/en-us/azure/iot-dps/about-iot-dps
You can find sample code for simulated devices in the docs: docs.microsoft.com/en-us/azure/iot-dps/quick-create-simulated-device-x509-csharp. Note that there are samples for different languages
My question is: how does a device provisioned with dps x509 certs then go to communicate with the hub with said cert.
Can we configure multiple iot devices applications running on a gateway ( single hardware ) with a single certificate signed for that gateway.?
Each of the device instance need to have it's own cert. However, when using group enrollment, they would all derive from the same root CA cert. See details in here: docs.microsoft.com/en-us/azure/iot-dps/concepts-security#attestation-mechanism
What is the demo script doing? How do the toasters know how to communicate with Azure? The Azure Docs are severely lacking..
The devices are connecting to the Device Provisioning Service in order to be provisioned automatically to the right instance of IoT Hub. You can find details in the docs here: docs.microsoft.com/en-us/azure/iot-dps/about-iot-dps
is the demo (code) already available ?
You can find sample code for simulated devices in the docs: docs.microsoft.com/en-us/azure/iot-dps/quick-create-simulated-device-x509-csharp. Note that there are samples for different languages