microsoftgraph / microsoftgraph/microsoft-graph-explorer-v4
Different result returned based on access token
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 260
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Different results returned for the same query from Graph Explorer and direct HTTP query.
To Reproduce
Steps to reproduce the behavior:
- Go to Graph Explorer
- Query this: https://graph.microsoft.com/v1.0/users?$expand=transitiveMemberOf($select=id,displayName)&$select=id
- The result contains all users; the ones without transitive membership has "transitiveMemberOf": [ ], and has a "@odata.nextLink" field for paging.
- Query the same with an access token for a registered app (using curl or similar)
- The result now only contains users with non-empty "transitiveMemberOf", and no "@odata.nextLink" for paging.
Expected behavior
The result in both cases are the same.
Screenshots
None, security reason.
Desktop (please complete the following information):
Not related to the problem.
Additional context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are mentioned. Start by reproducing the Graph Explorer and direct HTTP requests described in the issue, using equivalent queries and tokens; done would require identifying why the responses differ and documenting or fixing the discrepancy.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100