Azure-Samples / Azure-Samples/communication-services-javascript-quickstarts
ClientAuthError in manage-teams-identity-mobile-and-desktop
- Lenguaje dominante
- JavaScript
- Estrellas
- 108
- Forks
- 207
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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
Guía de contribución
Línea de trabajo
Comienza con el punto de entrada manage-teams-identity-mobile-and-desktop y reproduce el flujo de inicio de sesión en Windows 11 en http://localhost:3000. Inspecciona la traza de red para localizar la solicitud al endpoint de tokens de Microsoft identity platform y compara la URL de redirección de SPA configurada con la solicitud. La tarea está terminada cuando el callback se completa sin ClientAuthError y devuelve el ACS access token esperado.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- javascript
- Área
- authentication
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 30/100