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
We're facing this error: Error while authenticating. Extended authentication handler is not yet supported. with the Latest MQTT net release and Azure Event Grid MQTT Broker.
We have already tried the solution mentioned to recreate the certificate/user for the Broker, but this issue is frequent on two days basis on One particular Broker out of 3 setups.
Everything is consistent across deployment but the issue is faced with one broker only.
Which component is your bug related to?
Client
Server
To Reproduce
Steps to reproduce the behavior:
Using this version of MQTTnet '...'.
4.2.1.781, 4.3.7.1207
ExtendedAuthentication is supported with MQTT5, and usually used with OAUTH tokens, not sure what's the use case to use ExtendedAuth with certificates.
What is the change required here for the use of certificate @rido-min. We have been running same for past 1 year, this error started coming now. We have not mentioned protocol, hence it's using default which should be v3.1.
@pre-subham It seems that this feature is broken (regardless of certificates or other variant). There is a handler for that but not used when connecting.
I will add it and let you know when a test version is available.
Verification
Describe the bug
We're facing this error:
Error while authenticating. Extended authentication handler is not yet supported. with the Latest MQTT net release and Azure Event Grid MQTT Broker.
We have already tried the solution mentioned to recreate the certificate/user for the Broker, but this issue is frequent on two days basis on One particular Broker out of 3 setups.
Everything is consistent across deployment but the issue is faced with one broker only.
Which component is your bug related to?
To Reproduce
Steps to reproduce the behavior:
4.2.1.781, 4.3.7.1207
Expected behavior
Should connect without any issues.
Screenshots
The text was updated successfully, but these errors were encountered: