You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which version of Microsoft Identity Web are you using?
Note that to get help, you need to run the latest version.
Microsoft.Identity.Web 1.11
Where is the issue?
Web app
Sign-in users
Sign-in users and call web APIs
Web API
Protected web APIs (validating tokens)
Protected web APIs (validating scopes)
Protected web APIs call downstream web APIs
Token cache serialization
In-memory caches
Session caches
Distributed caches
Other (please describe)
Is this a new or an existing app?
b. The app is in production and I haven't upgraded Microsoft Identity Web, but started seeing this issue.
Expected behavior
When we set LogLevel to Debug or Trace in our appsettings, we expect verbose logs from Microsoft.Identity.Client.
Actual behavior
Instead, we only get Info logs from Microsoft.Identity.Client
Possible solution
In ConvertMicrosoftExtensionsLogLevelToMsal in TokenAcquisition.cs, reverse the order of the checks for IsEnabled(LogLevel.Information) and IsEnabled(LogLevel.Debug) || IsEnabled(LogLevel.Trace)
The text was updated successfully, but these errors were encountered:
Which version of Microsoft Identity Web are you using?
Note that to get help, you need to run the latest version.
Microsoft.Identity.Web 1.11
Where is the issue?
Is this a new or an existing app?
b. The app is in production and I haven't upgraded Microsoft Identity Web, but started seeing this issue.
Expected behavior
When we set LogLevel to Debug or Trace in our appsettings, we expect verbose logs from Microsoft.Identity.Client.
Actual behavior
Instead, we only get Info logs from Microsoft.Identity.Client
Possible solution
In ConvertMicrosoftExtensionsLogLevelToMsal in TokenAcquisition.cs, reverse the order of the checks for IsEnabled(LogLevel.Information) and IsEnabled(LogLevel.Debug) || IsEnabled(LogLevel.Trace)
The text was updated successfully, but these errors were encountered: