Skip to content

Commit 35e5ef2

Browse files
committed
jesusbar review
1 parent 8f300aa commit 35e5ef2

File tree

3 files changed

+19
-3
lines changed

3 files changed

+19
-3
lines changed

articles/iot-dps/concepts-x509-attestation.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,23 @@ Imagine that Contoso is a large corporation with its own Public Key Infrastructu
4949

5050
A *leaf certificate*, or *end-entity certificate*, identifies a certificate holder. It has the root certificate in its certificate chain and zero or more intermediate certificates. A leaf certificate is not used to sign any other certificates. It uniquely identifies a device to the provisioning service and is sometimes referred to as a *device certificate*. During authentication, a device uses the private key associated with its certificate to respond to a proof of possession challenge from the service.
5151

52-
## Use X.509 certificates with DPS
52+
## Prepare certificates
53+
54+
Devices use two different types of certificates when they connect to IoT Hub through DPS. When preparing your device, make sure you have all the proper certificates created and added to the device before connecting.
55+
56+
* Public root certificates: All devices need a copy of the public root certificates that IoT Hub, IoT Central, and Device Provisioning Service use to authorize connections.
57+
* Authentication certificates: X.509 certificates are the recommended method for authenticating a device identity.
58+
59+
### Required public root certificates
60+
61+
Azure IoT devices use TLS to verify the authenticity of the IoT hub or DPS endpoint they're connecting to. Each device needs a copy of the root certificate that IoT Hub and DPS use. We recommend that all devices include the following root CAs in their trusted certificate store:
62+
63+
* DigiCert Global G2 root CA
64+
* Microsoft RSA root CA 2017
65+
66+
For more information about recommended certificate practices, see [TLS support](./tls-support.md).
67+
68+
## Authentication using X.509 certificates
5369

5470
The provisioning service exposes two enrollment types that you can use to control device access with the X.509 attestation mechanism:
5571

articles/iot-dps/tls-support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ The following table summarizes which SDK versions support the trusted certificat
120120

121121
### Certificate pinning
122122

123-
[Certificate pinning](https://www.digicert.com/blog/certificate-pinning-what-is-certificate-pinning) and filtering of the TLS server certificates (also known as leaf certificates) and intermediate certificates associated with DPS endpoints is discouraged as Microsoft frequently rolls these certificates with little or no notice. If you must, only pin the root certificates as described in this [Azure IoT blog post](https://techcommunity.microsoft.com/t5/internet-of-things-blog/azure-iot-tls-critical-changes-are-almost-here-and-why-you/ba-p/2393169).
123+
[Certificate pinning](https://www.digicert.com/blog/certificate-pinning-what-is-certificate-pinning) and filtering of the TLS server certificates (also known as leaf certificates) and intermediate certificates associated with DPS endpoints is discouraged as Microsoft frequently rolls these certificates with little or no notice. If you must, only pin the root certificates.
124124

125125
## Use TLS 1.2 in the IoT SDKs
126126

articles/iot-hub/iot-hub-tls-support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The following table summarizes which SDK versions support the trusted certificat
4444

4545
### Certificate pinning
4646

47-
[Certificate pinning](https://www.digicert.com/blog/certificate-pinning-what-is-certificate-pinning) and filtering of the TLS server certificates (also known as leaf certificates) and intermediate certificates associated with IoT Hub endpoints is discouraged as Microsoft frequently rolls these certificates with little or no notice. If you must, only pin the root certificates as described in this [Azure IoT blog post](https://techcommunity.microsoft.com/t5/internet-of-things-blog/azure-iot-tls-critical-changes-are-almost-here-and-why-you/ba-p/2393169).
47+
[Certificate pinning](https://www.digicert.com/blog/certificate-pinning-what-is-certificate-pinning) and filtering of the TLS server certificates (also known as leaf certificates) and intermediate certificates associated with IoT Hub endpoints is discouraged as Microsoft frequently rolls these certificates with little or no notice. If you must, only pin the root certificates.
4848

4949
### Elliptic Curve Cryptography (ECC) server TLS certificate (preview)
5050

0 commit comments

Comments
 (0)