Amend documentation to recommend SAS tokens for authenticating downstream devices #125550
Conversation
…henticating downstream devices Result of IcM discussion here: https://portal.microsofticm.com/imp/v5/incidents/details/553315009/summary And direction from leadership to amend docs to reflect advising use of SAS tokens, not x.509 certs when using IoT Central.
|
@lev-i : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 7ce6678: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@dominicbetts Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
@lev-i - the change you're proposing is to the guidance around connecting standalone devices to IoT Central. Looking at the ICM, the specific problem encountered by the customer relates to connecting through an Azure IoT Edge gateway. The default guidance for connecting devices to IoT Central should remain as X.509. I think this guidance here contains the details for connecting IoT Edge devices through a gateway: https://learn.microsoft.com/en-us/azure/iot-edge/how-to-create-transparent-gateway?view=iotedge-1.5&tabs=iotedge |
|
#please-close |
Result of IcM discussion here:
https://portal.microsofticm.com/imp/v5/incidents/details/553315009/summary
And direction from leadership to amend docs to reflect advising use of SAS tokens, not x.509 certs when using IoT Central.