Urgent ADU client update to support 1.1.0 before August 2025 25 due to planned key rotation rendering ADU useless for devices in field #3101
Description
Query/Question
Your document: How to prepare for the rotation of a Device Update for IoT Hub root key
requires that we update our ADU Client to 1.1.0 from the current 1.0.0 before August 25 2025.
Why is this not a Bug or a feature Request?
You will be rotating keys on the 25 August 2025, rendering it impossible for us to use the ADU client for many devices in the field (UNLESS we update to 1.1.0 in good time).
Setup (please complete the following information if applicable):
- OS: [Windows 10 / 11]
- IDE: [VSCode Insiders]
- Version of the Library used: I'm using the main branch of the azure-iot-middleware-freertos
ESP32S3 (ESP-IDF 5.4)
We need to know how to do the update to our code base, and push this update through ADU to be ready for the key rotation that is going to occur on 25August 2025.
I'm sure that simply updating the following code from az_iot_adu_client.h:
from
/**
* @brief ADU Agent Version
*/
#define AZ_IOT_ADU_CLIENT_AGENT_VERSION "DU;agent/1.0.0"
to
/**
* @brief ADU Agent Version
*/
#define AZ_IOT_ADU_CLIENT_AGENT_VERSION "DU;agent/1.1.0"
will not suffice, as the manifest has probably been update for 1.1.0 as well.
Please as you can understand this is urgent.
See this issue opened on March 3, with no answer to date:
@florianhumblot Upgrade to ADU agent 1.1 #333