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
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/overview-mqtt.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.date: 07/15/2024
8
8
ms.service: azure-web-pubsub
9
9
ms.topic: overview
10
10
---
11
-
# Overview: MQTT in Azure Web PubSub service
11
+
# Overview: MQTT in Azure Web PubSub service (Preview)
12
12
13
13
[MQTT](https://mqtt.org/) is a lightweight pub/sub messaging protocol designed for devices with constrained resources. Azure Web PubSub service now natively supports MQTT over WebSocket transport.
14
14
@@ -18,6 +18,9 @@ You can use MQTT protocols in Web PubSub service for the following scenarios:
18
18
* Broadcast messages to MQTT clients.
19
19
* Get notifications for MQTT client lifetime events.
20
20
21
+
> [!NOTE]
22
+
> MQTT support in Azure Web PubSub is in preview stage.
23
+
21
24
## Key Features
22
25
23
26
### Standard MQTT Protocols Support
@@ -74,12 +77,12 @@ In general, a server to authenticate and authorize MQTT clients is required. The
74
77
75
78
* Workflow 1: The MQTT client gets a [JWT(JSON Web Token)](https://jwt.io) from somewhere with its credential, usually from an auth server. Then the client includes the token in the WebSocket upgrading request to the Web PubSub service, and the Web PubSub service validates the token and auth the client. This workflow is enabled by default.
76
79
77
-

80
+

78
81
79
82
* Workflow 2: The MQTT client sends an MQTT CONNECT packet after it establishes a WebSocket connection with the service, then the service calls an API in the upstream server. The upstream server can auth the client according to the username and password fields in the MQTT connection request, and the TLS certificate from the client. This workflow needs explicit configuration.
80
83
<!--Add link to tutorial and configuration-->
81
84
82
-

85
+

83
86
84
87
These two workflows can be used individually or in combination. If they're used in together, the auth result in the latter workflow would be honored by the service.
85
88
@@ -100,6 +103,11 @@ You can use REST API to do the following things:
100
103
101
104
[REST API specification for MQTT](./reference-rest-api-mqtt.md)
102
105
106
+
## Event Listener Support
107
+
108
+
> [!NOTE]
109
+
> Sending MQTT client events to Event Hubs is not supported yet.
0 commit comments