Skip to content

Commit 1e40e8d

Browse files
committed
Fix CLI parameters
1 parent c162df1 commit 1e40e8d

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

articles/iot-edge/how-to-authenticate-downstream-device.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -74,11 +74,11 @@ When you create the new device identity, provide the following information:
7474
You also can use the [IoT extension for Azure CLI](https://github.com/Azure/azure-iot-cli-extension) to complete the same operation. The following example uses the [az iot hub device-identity](/cli/azure/iot/hub/device-identity) command to create a new IoT device with symmetric key authentication and assign a parent device:
7575

7676
```azurecli
77-
az iot hub device-identity create -n {iothub name} -d {new device ID} --device-scope {deviceScope of parent device}.
77+
az iot hub device-identity create -n {iothub name} -d {new device ID} --device-scope {deviceScope of parent device}
7878
```
7979

8080
> [!TIP]
81-
> You can list device properties including device scope using `az iot hub device-identity list --hub-name {iothub name}`
81+
> You can list device properties including device scope using `az iot hub device-identity list --hub-name {iothub name}`.
8282
8383
Next, [Retrieve and modify the connection string](#retrieve-and-modify-connection-string) so that your device knows to connect via its gateway.
8484

@@ -132,9 +132,12 @@ For X.509 self-signed authentication, sometimes referred to as thumbprint authen
132132
You also can use the [IoT extension for Azure CLI](https://github.com/Azure/azure-iot-cli-extension) to complete the same device creation operation. The following example uses the [az iot hub device-identity](/cli/azure/iot/hub/device-identity) command to create a new IoT device with X.509 self-signed authentication and assigns a parent device:
133133
134134
```azurecli
135-
az iot hub device-identity create -n {iothub name} -d {device ID} --pd {gateway device ID} --am x509_thumbprint --ptp {primary thumbprint} --stp {secondary thumbprint}
135+
az iot hub device-identity create -n {iothub name} -d {device ID} --device-scope {deviceScope of gateway device} --am x509_thumbprint --ptp {primary thumbprint} --stp {secondary thumbprint}
136136
```
137137

138+
> [!TIP]
139+
> You can list device properties including device scope using `az iot hub device-identity list --hub-name {iothub name}`.
140+
138141
Next, [Retrieve and modify the connection string](#retrieve-and-modify-connection-string) so that your device knows to connect via its gateway.
139142

140143
### X.509 CA-signed authentication
@@ -176,9 +179,12 @@ This section is based on the IoT Hub X.509 certificate tutorial series. See [Und
176179
You also can use the [IoT extension for Azure CLI](https://github.com/Azure/azure-iot-cli-extension) to complete the same device creation operation. The following example uses the [az iot hub device-identity](/cli/azure/iot/hub/device-identity) command to create a new IoT device with X.509 CA signed authentication and assigns a parent device:
177180

178181
```azurecli
179-
az iot hub device-identity create -n {iothub name} -d {device ID} --pd {gateway device ID} --am x509_ca
182+
az iot hub device-identity create -n {iothub name} -d {device ID} --device-scope {deviceScope of gateway device} --am x509_ca
180183
```
181184

185+
> [!TIP]
186+
> You can list device properties including device scope using `az iot hub device-identity list --hub-name {iothub name}`.
187+
182188
Next, [Retrieve and modify the connection string](#retrieve-and-modify-connection-string) so that your device knows to connect via its gateway.
183189

184190
## Retrieve and modify connection string

0 commit comments

Comments
 (0)