Design of authentication mechanism #67
Description
Specification
3 MQTT Control Packets
├ 3.1 CONNECT – Connection Request
│├ 3.1.2 CONNECT Variable Header
││├ 3.1.2.8 User Name Flag
││├ 3.1.2.9 Password Flag
││└ 3.1.2.11 CONNECT Properties
││ ├ 3.1.2.11.9 Authentication Method
││ └ 3.1.2.11.10 Authentication Data
│└ 3.1.3 CONNECT Payload
│ ├ 3.1.3.5 User Name
│ └ 3.1.3.6 Password
└ 3.2 CONNACK – Connect acknowledgement
└ 3.2.2 CONNACK Variable Header
├ 3.2.2.3 CONNACK Properties
│├ 3.2.2.3.17 Authentication Method
│└ 3.2.2.3.18 Authentication Data
└ 3.15 AUTH – Authentication exchange
5.4.1 Authentication of Clients by the Server
The CONNECT packet contains User Name and Password fields. Implementations can choose how to make use of the content of these fields. They may provide their own authentication mechanism, use an external authentication system such as LDAP [RFC4511] or OAuth [RFC6749] tokens, or leverage operating system authentication mechanisms.
HiveMQ Blog
- Authentication with username and password
- Advanced Authentication Mechanisms
- X509 Client Certificate Authentication
- OAuth 2.0 & MQTT
EMQX Documentation
https://docs.emqx.com/en/emqx/latest/access-control/authn/authn.html