Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSAL.net is not handling dual headed accounts that share the same UPN for both an MSA and an AAD account. #4425

Closed
iulico-1 opened this issue Nov 17, 2023 · 0 comments · Fixed by #4419

Comments

@iulico-1
Copy link
Contributor

Library version used

4.57.0

.NET version

6.0.416

Scenario

PublicClient - desktop app

Is this a new or an existing app?

The app is in production, and I have upgraded to a new version of MSAL

Issue description and reproduction steps

Currently MSA passthrough doesn't work as expected for silent token acquisition flows because MSAL.net normalizes /organizations authority using accounts home tenant. This logic made sense for V1 requests, but it breaks MSA passthrough flows using the runtime.

Relevant code snippets

No response

Expected behavior

Application using /organizations can request ATs using MSA passthrough accounts

Identity provider

Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)

Regression

No response

Solution and workarounds

No response

@iulico-1 iulico-1 added untriaged Do not delete. Needed for Automation needs attention Delete label after triage labels Nov 17, 2023
@bgavrilMS bgavrilMS added bug P2 WAM public-client not_cpp_issue and removed untriaged Do not delete. Needed for Automation needs attention Delete label after triage labels Nov 17, 2023
@pmaytak pmaytak added this to the 4.58.0 milestone Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment