Skip to content

Commit fd66e5a

Browse files
Merge pull request #292990 from vicancy/patch-21
Update concept-client-protocols.md
2 parents 77cc635 + 6e526e3 commit fd66e5a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-web-pubsub/concept-client-protocols.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ You could also configure properties for the client connection when generating th
3737
| The `userId` for the client connection | `sub` | the userId | Only one `sub` claim is allowed. |
3838
| 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. |
3939
| 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. |
4141

4242
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).
4343

0 commit comments

Comments
 (0)