Skip to content

Commit 90ffdc8

Browse files
Merge pull request #291834 from kgremban/dec11-sfidps
SFI - ROPC - DPS
2 parents d322995 + 9867764 commit 90ffdc8

File tree

2 files changed

+12
-40
lines changed

2 files changed

+12
-40
lines changed

articles/iot-dps/quick-enroll-device-tpm.md

Lines changed: 8 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,7 @@ Although these steps work on both Windows and Linux computers, this article uses
3636

3737
* (Optional) If you want to enroll a simulated device at the end of this article, follow the procedure in [Create and provision a simulated TPM device](quick-create-simulated-device-tpm.md?pivots=programming-language-csharp) up to the step where you get an endorsement key for the device. Save the **Endorsement key**, as you use it later in this article.
3838

39-
> [!NOTE]
40-
> Don't follow the steps to create an individual enrollment by using the Azure portal.
39+
Don't follow the steps to create an individual enrollment by using the Azure portal.
4140
4241
:::zone-end
4342
@@ -47,8 +46,7 @@ Although these steps work on both Windows and Linux computers, this article uses
4746
4847
* (Optional) If you want to enroll a simulated device at the end of this article, follow the procedure in [Create and provision a simulated TPM device](quick-create-simulated-device-tpm.md?pivots=programming-language-nodejs) up to the step where you get an endorsement key and registration ID for the device. Save the **Endorsement key** and **Registration ID**, as you use them later in this article.
4948
50-
> [!NOTE]
51-
> Don't follow the steps to create an individual enrollment by using the Azure portal.
49+
Don't follow the steps to create an individual enrollment by using the Azure portal.
5250

5351
:::zone-end
5452

@@ -62,45 +60,13 @@ Although these steps work on both Windows and Linux computers, this article uses
6260

6361
* (Optional) If you want to enroll a simulated device at the end of this article, follow the procedure in [Create and provision a simulated TPM device](quick-create-simulated-device-tpm.md?pivots=programming-language-java) up to the step where you get an endorsement key for the device. Note the **Endorsement key** and the **Registration ID**, as you use them later in this article.
6462

65-
> [!NOTE]
66-
> Don't follow the steps to create an individual enrollment by using the Azure portal.
67-
68-
:::zone-end
69-
70-
## Get TPM endorsement key (Optional)
71-
72-
You can follow the steps in this article to create a sample individual enrollment. In this, case, you'll be able to view the enrollment entry in DPS, but you won't be able to use it to provision a device.
73-
74-
:::zone pivot="programming-language-csharp"
75-
76-
You can also choose to follow the steps in this article to create an individual enrollment and enroll a simulated TPM device. If you want to enroll a simulated device at the end of this article, follow the procedure in [Create and provision a simulated TPM device](quick-create-simulated-device-tpm.md?pivots=programming-language-csharp) up to the step where you get an endorsement key for the device. Save the **Endorsement key**, as you use it later in this article.
77-
78-
> [!NOTE]
79-
> Don't follow the steps to create an individual enrollment by using the Azure portal.
80-
81-
:::zone-end
82-
83-
:::zone pivot="programming-language-nodejs"
84-
85-
You can also choose to follow the steps in this article to create an individual enrollment and enroll a simulated TPM device. If you want to enroll a simulated device at the end of this article, follow the procedure in [Create and provision a simulated TPM device](quick-create-simulated-device-tpm.md?pivots=programming-language-nodejs) up to the step where you get an endorsement key and registration ID for the device. Save the **Endorsement key** and **Registration ID**, as you use them later in this article.
86-
87-
> [!NOTE]
88-
> Don't follow the steps to create an individual enrollment by using the Azure portal.
89-
90-
:::zone-end
91-
92-
:::zone pivot="programming-language-java"
93-
94-
You can also choose to follow the steps in this article to create an individual enrollment and enroll a simulated TPM device. If you want to enroll a simulated device at the end of this article, follow the procedure in [Create and provision a simulated TPM device](quick-create-simulated-device-tpm.md?pivots=programming-language-java) up to the step where you get an endorsement key for the device. Note the **Endorsement key** and the **Registration ID**, as you use them later in this article.
95-
96-
> [!NOTE]
97-
> Don't follow the steps to create an individual enrollment by using the Azure portal.
63+
Don't follow the steps to create an individual enrollment by using the Azure portal.
9864
9965
:::zone-end
10066
10167
## Get the connection string for your provisioning service
10268
103-
For the sample in this article, you'll need to copy the connection string for your provisioning service.
69+
For the sample in this article, you use the connection string for your provisioning service.
10470
10571
1. Sign in to the [Azure portal](https://portal.azure.com).
10672
@@ -226,6 +192,9 @@ This section shows you how to create a .NET Core console app that adds an indivi
226192
227193
:::zone pivot="programming-language-nodejs"
228194
195+
>[!TIP]
196+
>For simplicity, this sample uses SAS authentication to connect to the DPS service API. A more secure approach is to use Azure token credentials. For an example of that authentication method, see the [create_tpm_enrollment_with_token_credentials.js](https://github.com/Azure/azure-iot-sdk-node/blob/main/provisioning/service/samples/create_tpm_enrollment_with_token_credential.js) sample in the Node.js SDK.
197+
229198
1. From a command window in your working folder, run:
230199
231200
```cmd\sh
@@ -480,7 +449,7 @@ If you plan to explore the DPS tutorials, don't clean up the resources created i
480449
481450
## Next steps
482451
483-
In this article, you’ve programmatically created an individual enrollment entry for a TPM device. Optionally, you created a TPM simulated device on your computer and provisioned it to your IoT hub using the Azure IoT Hub Device Provisioning Service. To explore further, check out the following links:
452+
In this article, you programmatically created an individual enrollment entry for a TPM device. Optionally, you created a TPM simulated device on your computer and provisioned it to your IoT hub using the Azure IoT Hub Device Provisioning Service. To explore further, check out the following links:
484453
485454
* For more information about TPM attestation with DPS, see [TPM attestation](concepts-x509-attestation.md).
486455

articles/iot-dps/quick-enroll-device-x509.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.subservice: azure-iot-hub-dps
1616

1717
# Programmatically create a Device Provisioning Service enrollment group for X.509 certificate attestation
1818

19-
This article shows you how to programmatically create an [enrollment group](concepts-service.md#enrollment-group) that uses intermediate or root CA X.509 certificates. The enrollment group is created by using the [Azure IoT Hub DPS service SDK](libraries-sdks.md#service-sdks) and a sample application. An enrollment group controls access to the provisioning service for devices that share a common signing certificate in their certificate chain. To learn more, see [Use X.509 certificates with DPS](./concepts-x509-attestation.md#authentication-using-x509-certificates). For more information about using X.509 certificate-based Public Key Infrastructure (PKI) with Azure IoT Hub and Device Provisioning Service, see [X.509 CA certificate security overview](../iot-hub/iot-hub-x509ca-overview.md).
19+
This article shows you how to programmatically create an [enrollment group](concepts-service.md#enrollment-group) in Azure IoT Hub Device Provisioning Service (DPS) that uses intermediate or root CA X.509 certificates. The enrollment group is created by using the [Azure IoT service SDK](libraries-sdks.md#service-sdks) and a sample application. An enrollment group controls access to the provisioning service for devices that share a common signing certificate in their certificate chain. To learn more, see [Use X.509 certificates with DPS](./concepts-x509-attestation.md#authentication-using-x509-certificates). For more information about using X.509 certificate-based Public Key Infrastructure (PKI) with Azure IoT Hub and Device Provisioning Service, see [X.509 CA certificate security overview](../iot-hub/iot-hub-x509ca-overview.md).
2020

2121
## Prerequisites
2222

@@ -224,6 +224,9 @@ This section shows you how to create a .NET Core console application that adds a
224224

225225
This section shows you how to create a Node.js script that adds an enrollment group to your provisioning service.
226226

227+
>[!TIP]
228+
>For simplicity, this sample uses SAS authentication to connect to the DPS service API. A more secure approach is to use Azure token credentials. For an example of that authentication method, see the [create_tpm_enrollment_with_token_credentials.js](https://github.com/Azure/azure-iot-sdk-node/blob/main/provisioning/service/samples/create_tpm_enrollment_with_token_credential.js) sample in the Node.js SDK.
229+
227230
1. From a command window in your working folder, run:
228231

229232
```cmd\sh

0 commit comments

Comments
 (0)