Skip to content

Commit 517b362

Browse files
committed
add original identity section from client server arch doc
1 parent 39a9c92 commit 517b362

File tree

2 files changed

+40
-0
lines changed

2 files changed

+40
-0
lines changed
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
title: Identity model
3+
titleSuffix: An Azure Communication Services concept
4+
description: Learn about the identities and access tokens
5+
author: tophpalmer
6+
manager: sundraman
7+
services: azure-communication-services
8+
9+
ms.author: chpalm
10+
ms.date: 02/20/2025
11+
ms.topic: conceptual
12+
ms.service: azure-communication-services
13+
ms.subservice: identity
14+
---
15+
16+
This guide presents data flow diagrams for [Azure Communication Services](/azure/communication-services). Use these diagrams to understand how your clients and services interact with Azure to deliver communication experiences.
17+
18+
## Users authenticated via user access tokens
19+
20+
Communication Services clients present user access tokens to access, with improved security, the Azure calling and chat data plane. You should generate and manage user access tokens by using a trusted service. The token and the connection string or Microsoft Entra secrets that are necessary to generate them need to be protected. Failure to properly manage access tokens can result in additional charges because of misuse of resources.
21+
22+
:::image type="content" source="./media/architecture-identity.png" alt-text="Diagram that shows the user access token architecture." border="false":::
23+
24+
### Dataflow
25+
26+
1. A user starts the client application.
27+
2. The client application contacts your identity management service. The identity management service maintains a mapping between application identities and Communication Services identities. (Application identities include your users and other addressable objects, like services or bots.)
28+
3. The identity management service uses the mapping to [issue a user access token](/rest/api/communication/communication-identity/issue-access-token) for the applicable identity.
29+
30+
Azure App Service or Azure Functions are two alternatives for operating the identity management service. These services scale easily and have built-in features to [authenticate](/../../app-service/overview-authentication-authorization.md) users. They're integrated with [OpenID](../../app-service/configure-authentication-provider-openid-connect.md) and third-party identity providers like [Facebook](/../../app-service/configure-authentication-provider-facebook.md).
31+
32+
### Resources
33+
34+
- **Concept:** [User identity](/azure/communication-services/concepts/identity-model)
35+
- **Sample:** [Build an identity management service using Azure Functions](https://github.com/Azure-Samples/communication-services-authentication-hero-nodejs)
36+
37+
## Next steps
38+
39+
- [Authenticate to Azure Communication Services](./authentication.md).
40+
- [Create and manage access tokens](../quickstarts/identity/access-tokens.md).
30.4 KB
Loading

0 commit comments

Comments
 (0)