MQTT Client V5 Implementation (master branch) - #289
Merged
Conversation
ozangunalp
approved these changes
Jun 17, 2026
ozangunalp
left a comment
ozangunalp
left a comment
Contributor
There was a problem hiding this comment.
I think this is ok to be merged. We need to resolve the merge conflict but it shouldn't be too hard IMO.
Contributor
Contributor
|
@dometec can you rebase and fix the issue ? |
dometec
force-pushed
the
client_mqtt5_master
branch
from
June 18, 2026 09:28
04aabca to
0b6973e
Compare
Contributor
Author
|
done, let me check the CI-CD task failure... |
Contributor
Author
|
Waiting for #301 |
- Manage Publish v5 - Updated MqttEndpointImpl to handle PUBCOMP messages with reason codes. - Enhance authentication and subscription features - Modified MqttServerConnection to allow AUTH messages before CONNACK. - Added support for Wildcard and Shared Subscription properties in MqttConnAckMessage. - Implemented corresponding methods in MqttConnAckMessageImpl to retrieve new properties. - Introduced Mqtt5ClientAuthTest to validate enhanced authentication flow. - Added tests in Mqtt5ClientConnectTest for user properties in CONNECT packets. - Enhanced Mqtt5ClientDisconnectTest to verify server-initiated DISCONNECT handling. - Updated Mqtt5ClientPublishTest to check for maximum packet size enforcement. - Added tests in Mqtt5ClientSubscribeTest for handling of wildcard and shared subscriptions. - Created Mqtt5ClientWillTest to ensure correct encoding of will message properties. - Manage Server Redirect - Manage Subscription Identifier - Manage TopicAlias from Broker to Client Breaking Changes: - Removed willFlag client side (info derived from the presence of willtopic and willpayload, I removed also the new tests) - Will options serialized as object in json
…n current instance and add validation for QoS
…mpl, and add corresponding tests
…ication exchange during connecting state
…t-side authentication flow and provide example for SCRAM-SHA-256
…s and enhance example usage
…e direct message creation with authenticationExchange method
dometec
force-pushed
the
client_mqtt5_master
branch
from
June 22, 2026 08:52
28bb8b2 to
f6dd00f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implementation of MQTTv5 4.x branch ported on master branch.
This included all conversation mark resolved in #269