-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
MQTTv5 doesn't support oauth2 token re-authentication #12719
Comments
This is not a bug. I just updated our documentation to clearly list this limitation: While RabbitMQ supports OAuth 2.0 token renewal for AMQP 1.0, AMQP 0.9.1, and the RabbitMQ stream protocol, RabbitMQ does currently not support OAuth 2.0 token renewal for MQTT. I implemented token renewal for AMQP 1.0 very recently in #12599. This feature will be available in RabbitMQ 4.1. I implemented MQTT clients being disconnected upon token expiration recently in #11867. This feature got backported to RabbitMQ 4.0.x and RabbitMQ 3.13.x. |
@ansd |
@AntonSmolkov this is open source software you very likely pay nothing for, so you are welcome to contribute the features you need. Asking others "if they have plans" to implement something you need is not how open source software works. |
Describe the bug
The MQTT Plugin documentation states:
However, it seems an important part of the standard is missing—Re-authentication.
Currently, if I send an
AUTH
packet with a new token on existing connection, I receive anextended_authentication_unsupported
error. (source)I believe this is an essential part of the standard that should be implemented, as it is for AMQP-0-9-1 connections.
For reference, here is the description of the same feature implemented in Azure Event Grid: Authentication using Microsoft Entra JWT.
Reproduction steps
CONNECT
method, passing theJWT token
in the password field.AUTH
packet with reason code25 (re-authenticate)
and the renewedJWT token
.An error occurs:
extended_authentication_unsupported
.Expected behavior
JWT-token of the connection is updated
Additional context
No response
The text was updated successfully, but these errors were encountered: