Add api to read device ID from A7 application
We have a need for our A7 application to access the device ID.
Anonymous
shared this idea
Could you provide scenarios where you need to read device-ID?
2 comments
-
Anonymous
commented
We would like the devices to be able to "self-claim" themselves in our Tenant and in their Device Group at manufacturing time. Apps would include a call to a "claiming service", either offered by Microsoft as part of AS3, or we would build it for ourselves to streamline our manufacturing process.
This would eliminate the need for the manufacturer to handle Device IDs as part of the "Factory Floor Tasks", and to transfer them to us for the "Cloud Configuration Tasks".
The manufacturer would simply 1) "recover" the device to update the OS, 2) sideload our signed app that would include the "device self-claiming" code, and 3) add a WiFi network to enable default connectivity on the manufacturing line. (The current process would continue to exist for manufacturing lines without WiFi and Internet access.)
From there, the device should be able to add itself to a Device Group as a given Product if/when all functional tests complete successfully. After all, the OEM-signed code running inside the Azure Sphere environment is the most "trustworthy local OEM agent" to carry out these operations on behalf of the remote OEM.
-
Anonymous
commented
We have a proprietary cloud implementation that utilizes the device ID as part of a telemetry message from the device, not all our devices have to use an IoT Hub. Including the device ID in the message will allow us to continue to provide a common implementation at a high level that will continue to work across multiple devices (things). Without this feature, we'll need to treat Azure Sphere devices differently than the other devices in the system.
Is there a security concern with providing this api?