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/event-grid/mqtt-client-custom-jwt.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Microsoft Custom JWT authentication
2
+
title: Custom JWT authentication
3
3
description: Describes custom JWT authentication and authorization to publish or subscribe to MQTT messages
4
4
ms.topic: conceptual
5
5
ms.custom: build-2024
@@ -9,12 +9,12 @@ ms.author: seshanmugam
9
9
ms.subservice: mqtt
10
10
---
11
11
12
-
# Microsoft Custom JWT authentication and authorization to publish or subscribe to MQTT messages
12
+
# Custom JWT authentication and authorization to publish or subscribe to MQTT messages
13
13
14
14
You can authenticate MQTT clients with Custom JWT to connect to the Event Grid namespace. You can embed and validate custom claims in the JWT token to authorize publish or subscribe permissions to your Event Grid topic spaces.
15
15
16
16
> [!IMPORTANT]
17
-
> - This feature is supported only when using the MQTT v5 protocol version
17
+
> - This feature is supported only when using the MQTT v5 protocol version.
18
18
19
19
## Prerequisites
20
20
- You need an Event Grid namespace with MQTT enabled. Learn about [creating Event Grid namespace](/azure/event-grid/create-view-manage-namespaces#create-a-namespace)
@@ -25,7 +25,7 @@ You can authenticate MQTT clients with Custom JWT to connect to the Event Grid n
25
25
You can use the MQTT v5 CONNECT packet to provide the Custom JWT token to authenticate your client and the MQTT v5 AUTH packet to refresh the token.
26
26
27
27
> [!IMPORTANT]
28
-
> - If you don't set the CONNECT packet's authentication method to CUSTOM-JWT, you receive an 'invalid issuer'. error—even if all other configurations are correct.
28
+
> - If you don't set the CONNECT packet's authentication method to CUSTOM-JWT, you receive an 'invalid issuer' error—even if all other configurations are correct.
29
29
30
30
In the CONNECT packet, you can provide the required values in the following fields:
0 commit comments