Please fill out the form below before submitting, thank you!
[Y] Bug exists Release Version 1.2.5 ( Master Branch)
[N] Bug exists in MQTTv3 Client on Snapshot Version 1.2.6-SNAPSHOT (Develop Branch)
[Y] Bug exists in MQTTv5 Client on Snapshot Version 1.2.6-SNAPSHOT (Develop Branch)
During client connection establishment the only message allowed from the client is the CONNECT request. With MQTT 5 the AUTH message is also allowed to be sent. In fact it must be sent to finish authorizing the connection being established.
The fix ( see patch attached ) is to check that the message is either a CONNECT or an AUTH message and then allow the client to send it.
I also attach a simple test to highlight the client interaction during the connection authentication, this will require a broker that supports SASL to test
Please fill out the form below before submitting, thank you!
During client connection establishment the only message allowed from the client is the CONNECT request. With MQTT 5 the AUTH message is also allowed to be sent. In fact it must be sent to finish authorizing the connection being established.
The fix ( see patch attached ) is to check that the message is either a CONNECT or an AUTH message and then allow the client to send it.
I also attach a simple test to highlight the client interaction during the connection authentication, this will require a broker that supports SASL to test
SaslExampleTest.zip
auth.patch