Issue with Accessing D365 Business Central using user_impersonation permission.

Open
#1,504 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, typescript

Research direction

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.

Written by the indexing model from the issue text.

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

Dominant language
TypeScript
Stars
833
Forks
240
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoftgraph/msgraph-sdk-javascript

All issues in microsoftgraph/msgraph-sdk-javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.