[BUG] AcquireTokenSilentSupplier failed: Token not found in the cache #40654
Labels
Azure.Identity
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
tracking-external-issue
The issue is caused by external problem (e.g. OS) - nothing we can do to fix it directly
Describe the bug
Between msal4j versions 1.14.0 and 1.15.0 logging for AuthenticationErrorCode.CACHE_MISS has changed. I believe the change was accidental, resulting in additional (and potentially misleading) WARN messages being log.
Exception or Stack Trace
Our production system is logging "Execution of class com.microsoft.aad.msal4j.AcquireTokenSilentSupplier failed: Token not found in the cache" on "com.microsoft.aad.msal4j.ConfidentialClientApplication" logger (severity: WARN) every hour.
Expected behavior
Since cache miss simply triggers retrieval of a new token, I would expect this event (cache miss) to be logged with low severity. Preferably DEBUG level.
Setup (please complete the following information):
Additional context
in msal4j-1.14.0 AuthenticationResultSupplier there was:
logging CACHE_MISS on DEBUG level instead of ERROR.
in msal4j-1.15.0, there is only:
logging cache misses always on WARN level.
The text was updated successfully, but these errors were encountered: