Bug Fix: Logging During Authorization #129
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed a bug where if a
ClaimsPrincipal
was set by a piece of middleware in the seucrity pipleine, the default authentication middleware would inadvertently log a blank warning message since it didn't perform the authentication itself. The middleware now only logs messages if it attempts the authentication itselfFixed a bug where if a authorization challenge result was set by a piece of middleware in the security pipeline, the default authorization middleware would inadvertently log the challenge result , even when it did not determine this result itself. This could result double logging in some use scenarios. The default authorization component will now only log a challenge result it if produces the result itself.