Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/2294 below:

[Bug] Account deleted from MSAL cache when a bad_token result is received · Issue #2294 · AzureAD/microsoft-authentication-library-for-dotnet · GitHub

Logs and Network traces
Without logs or traces, it is unlikely that the team can investigate your issue. Capturing logs and network traces is described at https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/logging

Which Version of MSAL are you using ?
4.17.1

Platform
.net, .net core

What authentication flow has the issue?

• Desktop / Mobile
  • [x ] Interactive
  • Integrated Windows Auth
  • Username Password
  • Device code flow (browserless)
• Web App
  • Authorization code
  • OBO
• Daemon App
  • Service to Service calls

Other? - please describe;

Is this a new or existing app?
Visual studio
Repro

1. Have a user in multiple tenants where in one of the tenants the user is disabled.
2. Have an account with a short refresh token lifetime where an expired token message is sent from the server with a bad_token sub error

Expected behavior
Account should remain in the cache, but silent token acquisition attempts should throw an exception

Actual behavior
Account is deleted from the MSAL cache causing a cascading delete in VS.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4