Azure-Samples / Azure-Samples/communication-services-javascript-quickstarts
ClientAuthError in manage-teams-identity-mobile-and-desktop
- Langage dominant
- JavaScript
- Étoiles
- 108
- Forks
- 207
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
I want to call with an ACS resource related to my Microsoft Teams user (add-1-on-1-cte-video-calling). So to get the right ACS token, I wanted to get mine with the tool: manage-teams-identity-mobile-and-desktop
All environment variables are set, and it runs on the URL http://localhost:3000
http://localhost:3000/redirect is set on the Azure portal as a Single page application redirect URL for my Teams BOT.
So everything should be okay, but when I run this, after login my Teams User the callback URL called back, but not with the AccessToken, but this error
```
{"errorCode":"network_error","errorMessage":"Network request failed. Please check network trace to determine root cause. | Fetch client threw: Error: HTTP status code 400 | Attempted to reach: https://login.microsoftonline.com/[MY_TENANT_ID_HIDDEN]/oauth2/v2.0/token","subError":"","name":"ClientAuthError"}
```
Teams Bot has all the necessary permissions.
### This issue is for a: (mark with an `x`)
```
- [ x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```
### Minimal steps to reproduce
- run manage-teams-identity-mobile-and-desktop
- login with my Teams user
- get back the error above
### Any log messages given by the failure
>
### Expected/desired behavior
- I would like to get back the ACS access token of the impersonated Teams User
### OS and Version?
- Windows 11
### Versions
- code was downloaded a couple days ago
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par le point d’entrée manage-teams-identity-mobile-and-desktop et reproduisez le flux de connexion sur Windows 11 à l’adresse http://localhost:3000. Inspectez la trace réseau pour trouver la requête adressée au point de terminaison de jeton de Microsoft identity platform et comparez l’URL de redirection SPA configurée avec la requête. C’est terminé lorsque le callback s’achève sans ClientAuthError et renvoie l’ACS access token attendu.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript
- Domaine
- authentication
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 30/100