Release Device Management Client 4.13.0 General Availability · PelionIoT/mbed-cloud-client

Device Management Client

[Linux/Zephyr] Asynchronous DNS does not work well, and the device fails to reconnect to the cloud if some of the pods are restarted. In such a scenario, the device needs to be restarted.
To address this issue, the default DNS settings should be overridden to synchronous DNS in the application level:
- For Linux devices, set the PAL_DNS_API_VERSION flag to 0.
- For Zephyr devices, set the DNS API selection to POSIX.

Izuma branding changes.
Support for multiple ciphers via config flag PAL_MAX_ALLOWED_CIPHER_SUITES.
- This is required for improved LwM2M compliance.
- Please ensure your TLS configuration also enables the required ciphers.
Add support for parsing Pkcs#7 certificate format. This format is used in EST flow.
- This is required for improved LwM2M compliance.
Developer flow only: The device goes through a storage reset if the compiled credential file differs from the stored credentials.
In LWM2M_COMPLIANT mode, use Bootstrap server CA as LwM2M server CA for enabling server certificate verification during TLS handshake.
Fix compilation issue with glibc 2.34 and newer where PTHREAD stack sizes have been changed to runtime variables.
Alternating port fallback function for MBED_CLOUD_CLIENT_CUSTOM_URI_PORT added.
- If a socket error is encountered, the next try will be done with the original CoaP port 5684.
- After 2nd failure, we alternate back to the custom port.
- NOTE! Only port 443 can be used as an alternative customer port with Izuma Networks.