- 03/10/2021
- 5 minute de citit
In acest articol
Azure Communication Services este un serviciu identitar-agnostic. Acest design ofera multiple avantaje:
- Reutilizeaza identitatile existente din sistemul dvs. de gestionare a identitatii
- Ofera flexibilitate pentru scenarii de integrare
- Pastreaza identitatile dvs. private in Azure Communication Services
In loc sa duplicati informatii in sistemul dvs., veti mentine relatia de cartografiere necesara cazului dvs. de afaceri. De exemplu, puteti mapa identitati 1: 1, 1: N, N: 1, N: M. Identificatorii externi, cum ar fi numerele de telefon, utilizatorii, dispozitivele, aplicatiile si GUID-urile, nu pot fi folositi pentru identitate in Azure Communication Services. Jetoanele de acces care sunt generate pentru o identitate Azure Communication Services sunt utilizate pentru a accesa primitive, cum ar fi chatul sau apelarea.
Identitate
Puteti crea identitati utilizand biblioteca de identitate Azure Communication Services. O identitate serveste ca identificator in conversatii. Este folosit pentru a crea jetoane de acces. Aceeasi identitate ar putea participa la mai multe sesiuni simultane pe mai multe dispozitive. O identitate poate avea mai multe jetoane de acces activ in acelasi timp.
The deletion of an identity, resource, or subscription invalidates all of its access tokens. This action also deletes all data that’s stored for the identity. A deleted identity can’t create new access tokens or access previously stored data (for example, chat messages).
You aren’t charged for the number of identities you have. Instead, you’re charged for the use of primitives. The number of your identities doesn’t have to restrict how you map your application’s identities to the Azure Communication Services identities.
With the freedom of mapping comes privacy responsibility. If a user wants to be deleted from your system, then you need to delete all identities that are associated with that user.
Azure Communication Services doesn’t provide special identities for anonymous users. It doesn’t keep the mapping between the users and identities, and it can’t determine whether an identity is anonymous. You can design the identity concept to fit your needs. Our recommendation is to create a new identity for each anonymous user on each application.
Anyone who has a valid access token can access current identity content. For example, users can access chat messages that they sent. The access is restricted only to scopes that are part of the access token. For more information, see the Access tokens section in this article.
Identity mapping
Azure Communication Services doesn’t replicate the functionality of the Azure identity management system. It doesn’t provide a way for customers to use customer-specific identities. For example, customers can’t use a phone number or email address.
xxx incesto real sexogratis
porns sexo gratis
maduras a cuatro patas videos sexo
videos porno caseros en español mia kalifa
mi vecina me folla porno abuelas
peliculas porno gay en español videos de sexo gratis
videos pornos muy guarros pprno
porno amater español guarras españolas
se follan a mi mujer nicolette shea
peliculas porno de incesto gratis videos sexo gratis
videos guarros zofilia
travestis dotadas abuelas porno
andaluzas follando videos guarros
peliculas porno vintage maduras en playas nudistas
maduras gozando videos de investo
travestis españolas video sexo
xxxgay coñitos
gitana follando guarras.com
trios x videos guarros
se folla a su madre pelisxxx
Instead, Azure Communication Services provides unique identifiers. You can assign these unique identifiers to your application’s identities. Azure Communication Services doesn’t store any kind of information that might reveal the real identity of your users.
To avoid duplicating information in your system, plan how to map users from your identity domain to Azure Communication Services identities. You can follow any kind of pattern. For example, you can use 1:1, 1:N, N:1, or M:N. Decide whether a single user is mapped to a single identity or to multiple identities.
When a new identity is created, store its mapping to your application’s user or users. Because identities require access tokens to use primitives, the identity needs to be known to your application’s user or users.
If you use a relational database to store user information, then you can adjust your design based on your mapping scenario. For scenarios that map 1:1 or N:1, you might want to add a CommunicationServicesId column to the table to store your Azure Communication Services identity. In scenarios that use the relationship 1:N or N:M, you might consider creating a separate table in the relational database.
Access tokens
An access token is a JSON Web Token (JWT) that can be used to get access to Azure Communication Service primitives. An access token that’s issued has integrity protection. That is, its claims can’t be changed after it’s issued. So a manual change of properties such as identity, expiration, or scopes will invalidate the access token. If primitives are used with invalidated tokens, then access will be denied to the primitives.
The properties of an access token are:
- Identity.
- Expiration.
- Scopes.
An access token is always valid for 24 hours. After it expires, the access token is invalidated and can’t be used to access any primitive.
O identitate are nevoie de o modalitate de a solicita un nou jeton de acces de la un serviciu de pe server. Domeniu Parametrul defineste un set nevid de primitivele care pot fi utilizate. Azure Communication Services accepta urmatoarele domenii pentru jetoanele de acces.
Nume Descriere Chat Ofera posibilitatea de a participa la un chat VoIP Ofera posibilitatea de a apela identitati si numere de telefon
Pentru a revoca un jeton de acces inainte de expirarea acestuia, utilizati biblioteca de identitate Azure Communication Services. Revocarea jetonului nu este imediata. Propagarea dureaza pana la 15 minute. Eliminarea unei identitati, a unei resurse sau a unui abonament revoca toate jetoanele de acces.
Daca doriti sa eliminati capacitatea unui utilizator de a accesa anumite functionalitati, revocati toate jetoanele de acces. Apoi emiteti un nou jeton de acces care are un set de domenii mai limitat.
In Azure Communication Services, a rotation of access keys revokes all active access tokens that were created by using a former access key. All identities lose access to Azure Communication Services, and they must issue new access tokens.
We recommend issuing access tokens in your server-side service and not in the client’s application. The reasoning is that issuing requires an access key or a managed identity. For security reasons, sharing access keys with the client’s application isn’t recommended.
The client application should use a trusted service endpoint that can authenticate your clients. The endpoint should issue access tokens on their behalf. For more information, see Client and server architecture.
If you cache access tokens to a backing store, we recommend using encryption. An access token is sensitive data. It can be used for malicious activity if it’s not protected. Someone who has an access token can start the SDK and access the API. The accessible API is restricted only based on the scopes that the access token has. We recommend issuing access tokens that have only the required scopes.
Next steps
- For an introduction to access token management, see Create and manage access tokens.
- For an introduction to authentication, see Authenticate to Azure Communication Services.
- For an introduction to data residency and privacy, see Region availability and data residency.
