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/concept-client-protocols.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ You could also configure properties for the client connection when generating th
37
37
| The `userId` for the client connection |`sub`| the userId | Only one `sub` claim is allowed. |
38
38
| The lifetime of the token |`exp`| the expiration time | The `exp` (expiration time) claim identifies the expiration time on or after which the token MUST NOT be accepted for processing. |
39
39
| The [permissions](#permissions) the client connection initially has |`role`| the role value defined in [permissions](#permissions)| Specify multiple `role` claims if the client has multiple permissions. |
40
-
| The initial groups that the client connection joins once it connects to Azure Web PubSub |`group`| the group to join | Specify multiple `group` claims if the client joins multiple groups. |
40
+
| The initial groups that the client connection joins once it connects to Azure Web PubSub |`webpubsub.group`| the group to join | Specify multiple `webpubsub.group` claims if the client joins multiple groups. |
41
41
42
42
You could also add custom claims into the access token, and these values are preserved as the `claims` property in [connect upstream request body](./reference-cloud-events.md#system-connect-event).
0 commit comments