Mininum guaranteed date for DPS-TPM's "work as-is" ?

[neonsoftware]

Hi,

Regarding this sentence in the main README:

🚨We are announcing the deprecation of the utpm-c library support and DPS-TPM authentication support within the Azure IoT C-SDK.🚨 Starting May 2023, Microsoft will not provide support for this library. Existing applications using this library will continue to work as-is

There see that there is no guaranteed minimum guaranteed date specified for the work as-is.

Would it be possible to provide, according to your timeline a minimum guaranteed date, ex. will work as-is at least until Q4 2024 ?

Thank you very much in advance.
Have a nice day.

[ericwolz]

Currently there is no specific timeline as of yet. Any new projects should not take a dependency on native DPS-TPM authentication using this SDK,

C-SDK now supports OpenSSL ENGINEs: https://github.com/Azure/azure-iot-sdk-c/blob/master/iothub_client/devdoc/iothubclient_c_library.md#openssl-engine-examples
The second example is with TPM2.0 and X509 certificates using the TPM2 TSS OpenSSL Engine (https://github.com/tpm2-software/tpm2-tss-engine) with IoT Hub. Please let me know if you see any issues with DPS.

[neonsoftware]

Thank you for the prompt response, @ericwol-msft. I will report this to my team.

I have no further question. [the issue can be closed, should I ?]