-
Notifications
You must be signed in to change notification settings - Fork 77
Added proposal about adding an authentication support to MQTT bridge #200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Added proposal about adding an authentication support to MQTT bridge #200
Conversation
162cdbe to
d013354
Compare
132-add-auth-support-mqtt-bridge.md
Outdated
|
|
||
| ## Compatibility | ||
|
|
||
| We are currently using MQTT version 3.1.1. In future, if we consider to upgrade to MQTT version 5.0, which has introduced new features to address authentication, we will need to ensure that this proposal implements authentication and authorization support in a way that is compatible with both MQTT 3.1.1 and MQTT 5.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to move to MQTT 5.0 now instead of thinking about implementation compatible with both versions? That way you can implement the things directly based on the features introduced in 5.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
apart from not being a simple move, MQTT v3.1.1 is still the most used protocol in the industry. I had a conversation with @ppatierno a long ago, and seemed that there's no such plan to move to MQTT v5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm definitely not an expert in MQTT, but I read that v5 is still compatible with previous versions, as it supports v3.1 and v3.1.1 features. As I said, I'm not expert, but I guess it means that even if the MQTT v3.1.1 is the most used protocol, the clients would work with MQTT Bridge having the v5 there, or?
And yeah I understand that it's not a simple move. But if there are other benefits and the versions are compatible, I think it's something we could consider?
But yeah, I'm leaving this for @ppatierno as you two were working on it :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. Let's see what @ppatierno has to say about this move.
Meanwhile, I added some technical details to the proposal.
…rt for MQTT Bridge Signed-off-by: Antonio Pedro <[email protected]> Signed-off-by: Antonio Pedro <[email protected]>
Signed-off-by: Antonio Pedro <[email protected]>
3b708c9 to
b0f3a9b
Compare
Signed-off-by: Antonio Pedro <[email protected]>
Signed-off-by: Antonio Pedro <[email protected]>
This is a proposal to implement an authentication mechanism as requested by 84