[Bug] OneDrive ListRootFolder returns 502 BadGateway from API Hub
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
- Domain
- api, authentication, backend, cloud
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
- Is
ListRootFolderAsync()the right API - or shouldGetFilesFromFolderAsync()be used instead? - Does
/datasets/default/folderswork with MSI-authenticated connections? - 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
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.
More from Azure/Connectors-NET-Samples
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in Azure/Connectors-NET-Samples
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·