Skip to content

Commit eedca03

Browse files
committed
Specify cert chain for runtime installation
1 parent cd32056 commit eedca03

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/iot-edge/how-to-auto-provision-x509-certs.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: kgremban
55
manager: philmea
66
ms.author: kgremban
77
ms.reviewer: kevindaw
8-
ms.date: 04/02/2020
8+
ms.date: 04/09/2020
99
ms.topic: conceptual
1010
ms.service: iot-edge
1111
services: iot-edge
@@ -197,7 +197,7 @@ X.509 provisioning with DPS is only supported in IoT Edge version 1.0.9 or newer
197197
You'll need the following information when provisioning your device:
198198

199199
* The DPS **ID Scope** value. You can retrieve this value from the overview page of your DPS instance in the Azure portal.
200-
* The device identity certificate file on the device.
200+
* The device identity certificate chain file on the device.
201201
* The device identity key file on the device.
202202
* An optional registration ID (pulled from the common name in the device identity certificate if not supplied).
203203

@@ -209,7 +209,7 @@ Use the following link to install the Azure IoT Edge runtime on your device, usi
209209

210210
When you add the X.509 certificate and key information to the config.yaml file, the paths should be provided as file URIs. For example:
211211

212-
* `file:///<path>/identity_certificate.pem`
212+
* `file:///<path>/identity_certificate_chain.pem`
213213
* `file:///<path>/identity_key.pem`
214214

215215
The section in the configuration file for X.509 automatic provisioning looks like this:
@@ -227,7 +227,7 @@ provisioning:
227227
identity_pk: "<REQUIRED URI TO DEVICE IDENTITY PRIVATE KEY>"
228228
```
229229

230-
Replace the placeholder values for `scope_id`, `identity_cert`, `identity_pk` with the scope ID from your DPS instance, and the URIs to the cert and key file locations on your device. Provide a `registration_id` for the device if you want, or leave this line commented out to register the device with the CN name of the identity certificate.
230+
Replace the placeholder values for `scope_id`, `identity_cert`, `identity_pk` with the scope ID from your DPS instance, and the URIs to the cert chain and key file locations on your device. Provide a `registration_id` for the device if you want, or leave this line commented out to register the device with the CN name of the identity certificate.
231231

232232
Always restart the security daemon after updating the config.yaml file.
233233

@@ -237,7 +237,7 @@ sudo systemctl restart iotedge
237237

238238
### Windows device
239239

240-
Install the IoT Edge runtime on the device for which you generated the identity certificate and identity key. You'll configure the IoT Edge runtime for automatic, not manual, provisioning.
240+
Install the IoT Edge runtime on the device for which you generated the identity certificate chain and identity key. You'll configure the IoT Edge runtime for automatic, not manual, provisioning.
241241

242242
For more detailed information about installing IoT Edge on Windows, including prerequisites and instructions for tasks like managing containers and updating IoT Edge, see [Install the Azure IoT Edge runtime on Windows](how-to-install-iot-edge-windows.md).
243243

@@ -254,11 +254,11 @@ For more detailed information about installing IoT Edge on Windows, including pr
254254

255255
1. The **Initialize-IoTEdge** command configures the IoT Edge runtime on your machine. The command defaults to manual provisioning unless you use the `-Dps` flag to use automatic provisioning.
256256

257-
Replace the placeholder values for `{scope_id}`, `{identity cert path}`, and `{identity key path}` with the appropriate values from your DPS instance and the file paths on your device. If you want to specify the registration ID, include `-RegistrationId {registration_id}` as well, replacing the placeholder as appropriate.
257+
Replace the placeholder values for `{scope_id}`, `{identity cert chain path}`, and `{identity key path}` with the appropriate values from your DPS instance and the file paths on your device. If you want to specify the registration ID, include `-RegistrationId {registration_id}` as well, replacing the placeholder as appropriate.
258258

259259
```powershell
260260
. {Invoke-WebRequest -useb https://aka.ms/iotedge-win} | Invoke-Expression; `
261-
Initialize-IoTEdge -Dps -ScopeId {scope ID} -X509IdentityCertificate {identity cert path} -X509IdentityPrivateKey {identity key path}
261+
Initialize-IoTEdge -Dps -ScopeId {scope ID} -X509IdentityCertificate {identity cert chain path} -X509IdentityPrivateKey {identity key path}
262262
```
263263

264264
>[!TIP]

0 commit comments

Comments
 (0)