Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Bug - Preview version] IIdentityLogger does not log information created before serviceProvider is available
See original GitHub issueOnly LogLevel.Trace works to log the first line (header) of the Wilson logs. This is because, for all the other log levels, the logger instance is not created yet. The logger instance in ASP.NET Core version requires an IServiceProvider, which is created in Id. Web here, but the static instances in Wilson have already been initialized by ASP.NET Core, so the NullIdentityModelLogger is getting created, which sets IsEnabled to false. Logging gets enabled later, but the initial messages are not capture.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Verbose logs displayed by the static ctors are noisy and can be removed. The header information can be used as a substitute for view the Identity version.
Feature request was created to prefix error message with assembly version info to aid troubleshooting - https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/1852
Created a separate issue for missing header information - https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/1851