You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,22 @@ This repository contains the following libraries:
23
23
24
24
* Coming Soon: Azure IoT Device Provisioning Service Library
25
25
26
+
## Critical Upcoming Change Notice
27
+
28
+
All Azure IoT SDK users are advised to be aware of upcoming TLS certificate changes for Azure IoT Hub and Device Provisioning Service
29
+
that will impact the SDK's ability to connect to these services. In October 2022, both services will migrate from the current
30
+
[Baltimore CyberTrust CA Root](https://baltimore-cybertrust-root.chain-demos.digicert.com/info/index.html) to the
31
+
[DigiCert Global G2 CA root](https://global-root-g2.chain-demos.digicert.com/info/index.html). There will be a
32
+
transition period beforehand where your IoT devices must have both the Baltimore and Digicert public certificates
33
+
installed in their certificate store in order to prevent connectivity issues.
34
+
35
+
**Devices with only the Baltimore public certificate installed will lose the ability to connect to Azure IoT hub and Device Provisioning Service in October 2022.**
36
+
37
+
To prepare for this change, make sure your device's certificate store has both of these public certificates installed.
38
+
39
+
For a more in depth explanation as to why the IoT services are doing this, please see
0 commit comments