[Bug] Broker mode throwing Microsoft.Identity.Client.MsalServiceException

[keyuxuan]

Library version used

4.65.0

.NET version

.NET 8

Scenario

PublicClient - desktop app

Is this a new or an existing app?

The app is in production, I haven't upgraded MSAL, but started seeing this issue

Issue description and reproduction steps

When performing Broker mode, MSAL throws Microsoft.Identity.Client.MsalServiceException.
We have the CorrelationId ca261fb6-3701-466c-b5f9-fc6821bb34f9

Attached the error message, could you help take a look at and see what went wrong?

Relevant code snippets

No response

Expected behavior

No response

Identity provider

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

Regression

No response

Solution and workarounds

No response

[Ugonnaak1]

@keyuxuan are you running this program as the user who is currently logged into the system or as another user? You can check this by going to your Task Manager, go under the details tab, search for your app that is currently running and check if "User name" currently matches the user who is currently logged in

[mijpeterson]

Hi @Ugonnaak1, I can confirm that the app is being run under the logged in user.

[Ugonnaak1]

Hi @mijpeterson , would you mind sending a screenshot showing the program running alongside the username (same format as the screenshot I sent) so that I can confirm? Thank you!

[Ugonnaak1]

@keyuxuan , @mijpeterson would either of you be able to send a screenshot confirming that the program is running under the logged in user? Thank you!

[mijpeterson]

Hi @Ugonnaak1, apologies for the delay. I had not captured a screenshot but I was able to confirm on a pairing session with our customer that their user name was displayed next to the process that was running MSAL. I'm not super comfortable sharing their information (user alias) online without their permission. Is a screenshot absolutely necessary?

[Ugonnaak1]

Hi @mijpeterson, thanks for confirming. Based off this, it could be that they are running the program before they are successfully logged into their windows system. Would you mind providing the scenario that they are running or going through in which they encounter this problem

[Ugonnaak1]

Closing issue due to extended periods of no response. Please reopen if any further help is needed.