Skip to content

Commit 5e13493

Browse files
committed
Replace eacronym word ACS with Azure Communication Services
1 parent 6bd07ca commit 5e13493

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,9 @@ Each mid-call webhook callback sent by Call Automation uses a signed JSON Web To
3434
</dependency>
3535
```
3636

37-
4. Configure your application to validate the JWT and the configuration of your ACS resource. You need the `audience` values as it is present in the JWT payload.
37+
4. Configure your application to validate the JWT and the configuration of your Azure Communication Services resource. You need the `audience` values as it is present in the JWT payload.
3838
5. Validate the issuer, audience and the JWT token.
39-
- The audience is your ACS resource ID you used to set up your Call Automation client. Refer [here](../../../quickstarts/voice-video-calling/get-resource-id.md) about how to get it.
39+
- The audience is your Azure Communication Services resource ID you used to set up your Call Automation client. Refer [here](../../../quickstarts/voice-video-calling/get-resource-id.md) about how to get it.
4040
- The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys used to validate the JWT token. When the signature is valid and the token hasn't expired (within 5 minutes of generation), the client can use the token for authorization.
4141

4242
This sample code demonstrates how to configure OIDC client to validate webhook payload using JWT

0 commit comments

Comments
 (0)