[Bug] powerplatformadminv2 Failed to get OBO token from PFT exchange
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- azure, typescript
- Domain
- api, authentication
Research direction
Start by reproducing the Power Platform Admin V2 request in a private tab with an account requiring MFA, then compare the network request before and after signing in to portal.azure.com. Trace the OBO token exchange associated with the failing request; done means Code Apps load successfully without prior Azure portal authentication.
Written by the indexing model from the issue text.
Description
Describe the bug
Code Apps using Power Platform Admin V2 connections if opened in private tab (without prior authentication to Portal Azure fail with Failed to acquire OBO token: S2S33107: Failed to get OBO token from PFT exchange.
Steps to Reproduce
- Use account where 2FA is required to access Azure or triggered due to "AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access "
- Open Code App that leverages Power Platform Admin V2 connector for example https://github.com/Laskewitz/Power-Platform-Control-Hub
- Application fails on requests such as
https://6dd053988d8fe17a8e228f6b587e23.08.environment.api.powerplatform.com/connectors/runtime/invoke/scalegroups/usa002/shards/01/apis/powerplatformadminv2/connections//7fb2a23078d5450f8ad66b47650b7c02/resourcequery/resources/query?api-version=2024-10-01
Expected behavior
Content loads correctly
Actual behavior
400 Bad Request; after logging in to portal.azure.com with 2FA app is loading correctly
Screenshots or Error Messages
Additional context
Network logs sent to Code Apps Email.
- Dominant language
- TypeScript
- Stars
- 504
- Forks
- 145
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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 microsoft/PowerAppsCodeApps
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/PowerAppsCodeApps#465 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/PowerAppsCodeApps#464 · 1 comment · 5 reactions ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/PowerAppsCodeApps#463 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/PowerAppsCodeApps#462 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/PowerAppsCodeApps#461 ·
All issues in microsoft/PowerAppsCodeApps
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100