Skip to content

Commit 796e97f

Browse files
committed
required cert list added
1 parent eedca03 commit 796e97f

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,12 @@ Device identity certificates are only used for provisioning the IoT Edge device
4040

4141
After you create the device identity certificate, you should have two files: a .cer or .pem file that contains the public portion of the certificate, and a .cer or .pem file with the private key of the certificate. If you plan to use group enrollment in DPS, you also need the public portion of an intermediate or root CA certificate in the same certificate chain of trust.
4242

43+
You need the following files to set up automatic provisioning with X.509:
44+
45+
* The device identity certificate and its private key certificate. The device identity certificate is uploaded to DPS if you create an individual enrollment. The private key is passed to the IoT Edge runtime.
46+
* A full chain certificate, which should have at least the device identity and the intermediate certificates in it. The full chain certificate is passed to the IoT Edge runtime.
47+
* An intermediate or root CA certificate from the certificate chain of trust. This certificate is uploaded to DPS if you create a group enrollment.
48+
4349
### Use test certificates
4450

4551
If you don't have a certificate authority available to create new identity certs and want to try out this scenario, the Azure IoT Edge git repository contains scripts that you can use to generate test certificates. These certificates are designed for development testing only, and must not be used in production.

0 commit comments

Comments
 (0)