Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Breaking change between 8.0.2 and 8.1.0 #2926

Open
2 of 14 tasks
ssmelov opened this issue Oct 18, 2024 · 1 comment
Open
2 of 14 tasks

[Bug] Breaking change between 8.0.2 and 8.1.0 #2926

ssmelov opened this issue Oct 18, 2024 · 1 comment

Comments

@ssmelov
Copy link

ssmelov commented Oct 18, 2024

Which version of Microsoft.IdentityModel are you using?
8.0.2 and 8.1.0

Where is the issue?

  • M.IM.JsonWebTokens
  • M.IM.KeyVaultExtensions
  • M.IM.Logging
  • M.IM.ManagedKeyVaultSecurityKey
  • M.IM.Protocols
  • M.IM.Protocols.OpenIdConnect
  • M.IM.Protocols.SignedHttpRequest
  • M.IM.Protocols.WsFederation
  • M.IM.TestExtensions
  • M.IM.Tokens
  • M.IM.Tokens.Saml
  • M.IM.Validators
  • M.IM.Xml
  • S.IM.Tokens.Jwt
  • Other (please describe)

Description
There is a breaking change between version 8.0.2 and version 8.1.0 due to a modification in TokenValidationResult constructor's parameter.
During token validation, the JsonWebTokenHandler.ValidateTokenPayloadAsync method creates a TokenValidationResult instance. If Microsoft.IdentityModel.JsonWebTokens version 8.0.2 is used alongside Microsoft.IdentityModel.Tokens version 8.1.0, it throws a MissingMethodException.

@jennyf19
Copy link
Collaborator

@ssmelov We fixed this in 8.1.2: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/releases/tag/8.1.2

Can you try moving to the latest (8.1.2) instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants