Remove experimental code from TokenValidationResult#3259
Merged
Conversation
keegan-caruso
approved these changes
Jun 4, 2025
SummarySummary
CoverageMicrosoft.IdentityModel.JsonWebTokens - 80.3%
|
SummarySummary
CoverageMicrosoft.IdentityModel.JsonWebTokens - 80.3%
|
pmaytak
approved these changes
Jun 5, 2025
keegan-caruso
approved these changes
Jun 6, 2025
|
When used with Automapper we get the following error |
Collaborator
|
This is known. Make sure all the Microsoft.Identity.* packages (like Microsoft.Identity.JsonWebTokens) are of the same version (8.12.1). You can run |
This was referenced Jul 22, 2025
This was referenced May 4, 2026
Open
Closed
This was referenced May 11, 2026
chore(deps): Bump System.IdentityModel.Tokens.Jwt from 8.3.0 to 8.18.0
marcelocamargosjr/cashflow#38
Open
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Experimental code leaked into TokenValidationResult from early prototypes where we thought we could introduce a new 'non throwing' model using existing objects.
This turned out to be hard and confusing, so we moved to new types, however this code was left in the repo.