Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Issue with Accessing D365 Business Central using user_impersonation permission.

Ouverte
#1,504 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Bug
Clarté
À clarifier
Activité
À l'abandon
Stack technique
node.js, typescript
Domaine
api, authentication

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
TypeScript
Étoiles
833
Forks
240
Aucune PR mergée en 30 j

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoftgraph/msgraph-sdk-javascript

Toutes les issues de microsoftgraph/msgraph-sdk-javascript

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.