Skip to content

Commit f3cd370

Browse files
authored
Update secure-webhook-endpoint.md
add websocket authentication
1 parent d432c26 commit f3cd370

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

articles/communication-services/how-tos/call-automation/secure-webhook-endpoint.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ services: azure-communication-services
1515
zone_pivot_groups: acs-js-csharp-java-python
1616
---
1717

18-
# How to secure webhook endpoint
18+
# How to secure webhook endpoints and websocket connections
1919

2020
Securing the delivery of messages from end to end is crucial for ensuring the confidentiality, integrity, and trustworthiness of sensitive information transmitted between systems. Your ability and willingness to trust information received from a remote system relies on the sender providing their identity. Call Automation has two ways of communicating events that can be secured; the shared IncomingCall event sent by Azure Event Grid, and all other mid-call events sent by the Call Automation platform via webhook.
2121

@@ -45,6 +45,23 @@ A common way you can improve this security is by implementing an API KEY mechani
4545
[!INCLUDE [Secure webhook endpoint with Python](./includes/secure-webhook-endpoint-python.md)]
4646
::: zone-end
4747

48+
## Call Automation websockets events
49+
### Authentication Token in WebSocket Header
50+
Each WebSocket connection request made by Call Automation now includes a signed JSON Web Token (JWT) in the Authentication header. This token can be validated using standard OpenID Connect (OIDC) JWT validation methods.
51+
- The JWT has a lifetime of 24 hours.
52+
- A new token is generated for each connection request to your WebSocket server.
53+
- More details are available in the official documentation:
54+
Secure webhook endpoint – Azure Communication Services
55+
56+
### Additional Headers:
57+
The Correlation ID and Call Connection ID are now included in the WebSocket headers for improved traceability.
58+
59+
## IP Range
60+
| Category | IP ranges or FQDN | Ports |
61+
| :-- | :-- | :-- |
62+
| Call Automation Media | 52.112.0.0/14, 52.122.0.0/15, 2603:1063::/38| UDP: 3478, 3479, 3480, 3481|
63+
| Callback URLs | *.lync.com, *.teams.cloud.microsoft, *.teams.microsoft.com, teams.cloud.microsoft, teams.microsoft.com 52.112.0.0/14, 52.122.0.0/15, 2603:1027::/48, 2603:1037::/48, 2603:1047::/48, 2603:1057::/48, 2603:1063::/38, 2620:1ec:6::/48, 2620:1ec:40::/42 | TCP: 443, 80 UDP: 443 |
64+
4865
## Next steps
4966

5067
- Learn more about [How to control and steer calls with Call Automation](../call-automation/actions-for-call-control.md).

0 commit comments

Comments
 (0)