Skip to content

Commit 34a2766

Browse files
Add notice about upcoming service TLS changes to the readme (#826)
* Add notice about upcoming service TLS changes to the readme * Update README.md
1 parent c6a7be3 commit 34a2766

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,22 @@ This repository contains the following libraries:
2323

2424
* Coming Soon: Azure IoT Device Provisioning Service Library
2525

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
40+
[this article](https://techcommunity.microsoft.com/t5/internet-of-things/azure-iot-tls-critical-changes-are-almost-here-and-why-you/ba-p/2393169).
41+
2642
## Installing the libraries
2743

2844
Pip installs are provided for all of the SDK libraries in this repo:

0 commit comments

Comments
 (0)