You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it appears that if the client sends a CONNECT packet using MQTT 5 extended authentication (i.e., it sets the Authentication Method) and it receives an AUTH packet from the server instead of a CONNACK packet, it will throw an exception:
thrownewNotSupportedException("Extended authentication handler is not yet supported");
}
This means that the client cannot connect using extended authentication with AUTH packets being exchanged. It looks like this feature gap is not being tracked, so I am opening this issue to track it.
The text was updated successfully, but these errors were encountered:
This is related to issue #2095. That issue is closed and resolved with pull request #2132. This issue should be closed as it is resolved by the same pull request.
Currently, it appears that if the client sends a
CONNECT
packet using MQTT 5 extended authentication (i.e., it sets the Authentication Method) and it receives anAUTH
packet from the server instead of aCONNACK
packet, it will throw an exception:MQTTnet/Source/MQTTnet/Client/MqttClient.cs
Lines 466 to 469 in e18a91a
This means that the client cannot connect using extended authentication with AUTH packets being exchanged. It looks like this feature gap is not being tracked, so I am opening this issue to track it.
The text was updated successfully, but these errors were encountered: