Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Issue with Accessing D365 Business Central using user_impersonation permission.

Aberta
  • Algo errado?
#1,504 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
25/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Stack de tecnologia
node.js, typescript
Domínio
api, authentication

Direção de pesquisa

Begin at the microsoft-graph-client API call and the access-token acquisition described in the report; verify the SDK version 2.2.1, Node 14.19.1, and the token's scp value. Done means reproducing the missing user_impersonation scope or establishing that the issue is outside this SDK with enough configuration or API details for follow-up.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Bug Report

I am developing Microsoft Teams BOT using yo Teams and Node.

The requirement is to access the Business Central using the BOT to fetch the environment with the user's delegated permission.

I am able to configure the BOT, App service and also able to fetch the currently logged-in users' details.

But the scp parameter of the Access Token is not returning the user_impersonation scope in int. Hence, it's not working for me to access the Business Central.

Here are the screenshot of the permission. enter image description here

Any help is appreciated.

NOTE: I am using the microsoft-graph-client library to perform this API Call.

Prerequisites

  • Can you reproduce the problem?
  • Are you running the latest version?
  • Are you reporting to the correct repository?
  • Did you perform a cursory search?

For more information, see the CONTRIBUTING guide.

Description

[Description of the bug or feature]

Console Errors: [Is there any console error]
No
Screenshots: [If applicable, add screenshots to help explain your problem]
image

Steps to Reproduce

  1. [First Step]
  2. [Second Step]
  3. [and so on...]

Expected behavior: [What you expected to happen]
The response token should have the scp of user_impersonation.

Actual behavior: [What actually happened]
The response token does not have the scp of user_impersonation.

Additional Context

Add any other context about the problem here..

Usage Information

Request ID - Value of the requestId field if you are receiving a Graph API error response

SDK Version - [SDK version you are using]
2.2.1

  • Node (Check, if using Node version of SDK)

Node Version - [The version of Node you are using]
14.19.1

  • Browser (Check, if using Browser version of SDK)

Browser Name - [The name of Browser that you are using for SDK]
EDGE
Version - [The version of the browser you are using]
117.0.2045.41

Linguagem predominante
TypeScript
Estrelas
834
Forks
240
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoftgraph/msgraph-sdk-javascript

Todas as issues de microsoftgraph/msgraph-sdk-javascript

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.