Skip to content

Commit 66e0870

Browse files
authored
Increase claribility
1 parent 4e42393 commit 66e0870

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/azure-web-pubsub/howto-configure-application-firewall.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,10 +10,10 @@ ms.author: biqian
1010
---
1111
# Application Firewall (Preview) for Azure Web PubSub Service
1212

13-
The Application Firewall provides sophisticated control over client connections in a distributed system. Before diving into its functionality and setup, let's clarify what the Application Firewall does not do:
13+
The Application Firewall provides sophisticated control over client connections in a distributed system. Before diving into its functionality and setup, let's clarify what the Application Firewall doesn't do:
1414

15-
1. It does not replace authentication. The firewall operates behind the client connection authentication layer.
16-
2. It is not related to network layer access control.
15+
1. It doesn't replace authentication. The firewall operates behind the client connection authentication layer.
16+
2. It isn't related to network layer access control.
1717

1818
## What Does the Application Firewall Do?
1919

@@ -88,7 +88,7 @@ resource webpubsub 'Microsoft.SignalRService/webpubsub@2024-10-01-preview' = {
8888
maxCount: 10
8989
}
9090
]
91-
clientTrafficControlRules:[
91+
clientTrafficControlRules: [
9292
// Add or remove rules as needed
9393
{
9494
// This rule will be skipped if no userId is set
@@ -123,7 +123,7 @@ Deploy the Bicep file using Azure CLI
123123

124124
## Configure access token
125125

126-
The application firewall rules only take effect when the access token contains the corresponding claim. A rule is **skipped** if the connection does not have the corresponding claim. *userId" and *roles* are currently supported claims in the SDK.
126+
The application firewall rules only take effect when the access token contains the corresponding claim. A rule is **skipped** if the connection doesn't have the corresponding claim. *userId" and *roles* are currently supported claims in the SDK.
127127

128128
Below is an example to add userId and insert a unique placeholder in the access token:
129129

0 commit comments

Comments
 (0)