-
Hello There, I am upgrading from MQTTv3.1.1 to MQTTv5. The same certificates work fine on v3.1.1, but I'm encountering an error with v5. I've tried creating new certificates on AWS IoT Core, but that didn't solve the issue. It seems there are no specific settings on the AWS side for the v5 version. I'm currently stuck and would appreciate any help. Here is the trace: [TRACE] [2024-08-06T21:44:03Z] [0000cc30] [channel] - id=000002127F3CEB70: sending read message of size 113, from slot 000002127DCB4010 to slot 000002127DCB4060 with handler 000002127D965118. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
You're getting hung up on when the broker receives the CONNECT packet. This is usually due to a permission policy problem. Is the log from the new cert/key pair? There is absolutely no difference connecting with mqtt3 vs mqtt5 when it comes to authentication mechanisms (x509 mtls, websockets over sigv4, etc...) Things to check include:
|
Beta Was this translation helpful? Give feedback.
The issue has been resolved. I was following the instructions in the README, https://github.com/aws/aws-iot-device-sdk-java-v2/blob/main/samples/Mqtt5/PubSub/README.md but it didn't mention adding the necessary connection properties, particularly the client ID. I missed this step, and since we have some policies configured to validate the client ID, this was the cause of the problem. Thanks for your help.