nRF Connect MQTT returns -22 invalid argument

RE: nRF Connect MQTT returns -22 invalid argument

dejans — Tue, 19 Jul 2022 08:13:16 GMT

Hi Frank,

Thank you for this information.

I am glad to hear that everything is working out well for now.

Best regards,
Dejan

RE: nRF Connect MQTT returns -22 invalid argument

fhfs — Tue, 19 Jul 2022 06:52:03 GMT

I was able to connect to the Azure IoT Hub using the zephyr dns and the Openthread network, and I got an error in the MQTT Connack. I supplied bad credentials, this was expected. This is all based on the Zephyr Azure sample.

I am now trying to get the nRF Connect SDK's Azure Sample working. Because we use DPS, for our device provisioning. I will let you know, if it doesnt work, but it seems very possible.

RE: nRF Connect MQTT returns -22 invalid argument

dejans — Mon, 18 Jul 2022 08:20:43 GMT

Hi Frank,

Could you please provide information about the current status?

Best regards,
Dejan

RE: nRF Connect MQTT returns -22 invalid argument

fhfs — Fri, 15 Jul 2022 20:51:16 GMT

I had to modify the broker_init function to support ipv6 instead of ipv4.

RE: nRF Connect MQTT returns -22 invalid argument

brown27 — Thu, 14 Jul 2022 21:31:52 GMT

Hello, looks like some nice work! Out of curiosity, how much have you had to adapt the Azure IoT Hub sample and other files so far (other than the prj.conf and MBedTLS that you showed here)?

RE: nRF Connect MQTT returns -22 invalid argument

fhfs — Mon, 11 Jul 2022 11:37:42 GMT

I tracked the error to mbedtls_x509_crt_parse failed

Where it failed with error -9774 (-0x262e). Google showed this means "Signature algorithm (oid) isunsupported"

It had trouble parsing the certificate because it was missing the proper algorithms to parse them.

So I enabled the required algorithms in MBedTLS.

For me this was:

#define MBEDTLS_ECDSA_C
#define MBEDTLS_SHA256_C
#define MBEDTLS_RSA_C
#define MBEDTLS_AES_C
#define MBEDTLS_PKCS1_V21

Now the TCP TLS connection connects and returns handshake error -0x7280