DPS connection issue. about iot-middleware-freertos-samples HOT 8 CLOSED

Hi @aardrasystems
The registration ID is not the same thing as the enrollment group. The provisioning service needs a way to distinguish devices from each other and the registration ID is how this is done. It seems like you are using SAS key group enrollment so for that here is the documentation just in case: https://docs.microsoft.com/en-us/azure/iot-dps/concepts-symmetric-key-attestation?tabs=linux#group-enrollments

from iot-middleware-freertos-samples.

Thanks
Thanks, I will read the document?

Is it possible to find this Azure Device Provisioning Service Registration ID in the portal, so that I can get the demo running with DPS?

Is it possible to use the SAS token with ADP?

from iot-middleware-freertos-samples.

The registration ID is determine by you. From the docs using Azure CLI:

az iot dps compute-device-key --key 8isrFI1sGsIlvvFSSFRiMfCNzv21fjbE/+ah/lSh3lF8e2YG1Te7w1KpZhJFFXJrqYKi9yegxkqIChbqOS9Egw== --registration-id sn-007-888-abc-mac-a1-b2-c3-d4-e5-f6

That last part is a unique registration ID which you can come up with.

from iot-middleware-freertos-samples.

Ok, so that I have understood it correct:

I replace "8isrFI1sGsIlvvFSSFRiMfCNzv21fjbE/+ah/lSh3lF8e2YG1Te7w1KpZhJFFXJrqYKi9yegxkqIChbqOS9Egw=="
With my primary key for my enrollment group?

But when it comes to REG_ID, I believe this is the device's ID. How would I know this ID?

What i was hoping to do is apply DPS to multiple devices,for it to join the IoTHub.

from iot-middleware-freertos-samples.

The primary key comes from here:

The registration key must be different for each device so you can't use the same one for all of them. For more details on what registration ids and device ids are used for, please see here: https://docs.microsoft.com/en-us/azure/iot-dps/concepts-service#registration-id

from iot-middleware-freertos-samples.

Hi @aardrasystems I'm going to go ahead and close this for now. Please let us know if you would like it reopened.

from iot-middleware-freertos-samples.

Hi, @danewalton I am just wondering if the registration ID which is supposed to be unique(can be a Mac ID of ESP 32) uses a group enrollment primary key to generate a device key that is to be fed as a symmetric key. https://learn.microsoft.com/en-us/azure/iot-dps/how-to-legacy-device-symm-key?tabs=windows&pivots=programming-language-ansi-c#derive-a-device-key

but ideally, it should fetch the Mac address and generate the device key using the group enrollment primary key it self!

from iot-middleware-freertos-samples.

For group enrollments, the registration ID is the device ID. Devices should not store the group enrollment primary key, but the device key used for enrollment should be generated externally and and configured on the device.

https://learn.microsoft.com/en-us/azure/iot-dps/concepts-service

from iot-middleware-freertos-samples.