MsalClientException exception thrown when token not found in cache #38300
Labels
Azure.Identity
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
feature-request
This issue requires a new behavior in the product in order be resolved.
Milestone
Describe the bug
When a token is not found in the in-memory cache then Azure identity log it as an MSAL exception.
The log level is a bit misleading if there is a cache miss. A warning level log might be better suited than an error log.
Or is it that I am missing something to configure it properly to avoid
ERROR
level log on cache miss?Exception or Stack Trace
12:40:39.710 [ForkJoinPool.commonPool-worker-1] DEBUG c.m.a.m.ConfidentialClientApplication - [Correlation ID: f1f20e6d-42d7-4b54-baa8-7f74934320e0] Execution of class com.microsoft.aad.msal4j.AcquireTokenSilentSupplier failed.
To Reproduce
Steps to reproduce the behavior:
Code Snippet
Add the code snippet that causes the issue.
Expected behavior
Logging cache miss at a warning level might be better than logging it at error level.
Screenshots
NA
Setup (please complete the following information):
Additional context
NA
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: