[Bug] OneDrive ListRootFolder returns 502 BadGateway from API Hub

Open
#45 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
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
azure, csharp

Research direction

Start by reproducing GET /api/onedrive/root and trace ListRootFolderAsync() to the /datasets/default/folders call. Compare that path with GetFilesFromFolderAsync() and inspect the MSI-authenticated connection for the reported API Hub 502. Done means identifying whether the failure is in the selected API, MSI connection configuration, or API Hub, with a verified working path or documented blocker.

Written by the indexing model from the issue text.

Description

Summary

The onedrive/root endpoint consistently returns 502 BadGateway from the API Hub, both locally and in Azure deployment.

Repro

GET https://sdk-connector-samples.azurewebsites.net/api/onedrive/root

Error

The connector calls GET /datasets/default/folders which returns 502 from the API Hub gateway (source: 0a8e3a9fa83240839c163637de5e83f0.08.common.logic-df.azure-apihub.net, innerError status 500).

Questions to investigate

  1. Is ListRootFolderAsync() the right API - or should GetFilesFromFolderAsync() be used instead?
  2. Does /datasets/default/folders work with MSI-authenticated connections?
  3. Is this a transient API Hub issue or a connection configuration problem?

Connection details

  • Namespace: sdk-test-gateway (nsUrlId: 0a8e3a9fa83240839c163637de5e83f0)
  • Connection: onedriveforbusiness-test
  • MSI ACL: granted (objectId d77681c2-bb7f-4b90-ba93-2b9cee96cbae)
Dominant language
C#
Stars
3
Forks
3
Avg merge
1h 8m
Merged PRs (30d)
2

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 Azure/Connectors-NET-Samples

All issues in Azure/Connectors-NET-Samples

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.