Ashok Kumar Ramakrishnan
Ashok Kumar Ramakrishnan
hi @aries-zhang - I was able to repro the issue of prompting for default OS account. For some reason, when you use the VisualStudio client ID in the MSAL.NET sample...
@aries-zhang - the account cache in MSALRuntime layer comes from all apps. This is by design. MSALRuntime will likely have more accounts than in WAM in some cases. And there...
@msJinLei - The issue is understood now and we are actively working on the fix. Will update around mid next week on the progress and ETA for the final fix.
I am actively working on the fix. ETA for the fix to be checked in is by 06/14. I will see if I can release the fix as well within...
@AlyaKoni - Are you running the PS as administrator? The logs point to an issue that we fixed recently when running as admin. Not sure if it fully explains why...
When your resource server rejects the token, do another acquireTokenSilentAsync call setting .WithForceRefresh. https://learn.microsoft.com/en-us/dotnet/api/microsoft.identity.client.acquiretokensilentparameterbuilder.withforcerefresh?view=msal-dotnet-latest&viewFallbackFrom=azure-dotnet
@jiasli - I am going to close this for now. Feel free to reopen when you have a repro of the issue.
We will work on the fix this week. Will update when there is something to share.
@bojordan - This issue has been fixed already. Make sure Microsoft.Identity.Client.NativeInterop version is 0.16.2
We haven't heard about Interactive sign in flow issues or caching issues from anyone else in the community. This is most likely an integration issue. Please refer to the MSAL.NET...