Skip to content

Commit 7e9918f

Browse files
Merge pull request #219397 from AshokPeddakotla-MSFT/patch-83
(Azure CXP) Fixing a typo in token creation step
2 parents 69698b8 + dc2fcd2 commit 7e9918f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/iot-hub/iot-hub-dev-guide-sas.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -365,7 +365,7 @@ Here are the main steps of the token service pattern:
365365

366366
2. When a device/module needs to access your IoT hub, it requests a signed token from your token service. The device can authenticate with your custom identity registry/authentication scheme to determine the device/module identity that the token service uses to create the token.
367367

368-
3. The token service returns a token. The token is created by using `/devices/{deviceId}` or `/devices/{deviceId}/module/{moduleId}` as `resourceURI`, with `deviceId` as the device being authenticated or `moduleId` as the module being authenticated. The token service uses the shared access policy to construct the token.
368+
3. The token service returns a token. The token is created by using `/devices/{deviceId}` or `/devices/{deviceId}/modules/{moduleId}` as `resourceURI`, with `deviceId` as the device being authenticated or `moduleId` as the module being authenticated. The token service uses the shared access policy to construct the token.
369369

370370
4. The device/module uses the token directly with the IoT hub.
371371

@@ -410,4 +410,4 @@ If you would like to try out some of the concepts described in this article, see
410410

411411
* [Get started with Azure IoT Hub](../iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-nodejs)
412412
* [How to send cloud-to-device messages with IoT Hub](iot-hub-csharp-csharp-c2d.md)
413-
* [How to process IoT Hub device-to-cloud messages](tutorial-routing.md)
413+
* [How to process IoT Hub device-to-cloud messages](tutorial-routing.md)

0 commit comments

Comments
 (0)