Resolve a signing key using both KeyId and X5t in a consistent manner #2061
Conversation
This file contains 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
dannybtsai
requested review from
brentschmaltz,
victorm-hernandez,
sruke,
ciaozhang and
TimHannMSFT
…gningKeyUsingValidationParameters() and updated the test
brentschmaltz
approved these changes
Apr 25, 2023
brentschmaltz
requested changes
Apr 25, 2023
brentschmaltz
approved these changes
Apr 26, 2023
renovate bot
referenced
this pull request
in orso-co/Orso.Arpa.Api
May 3, 2023
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [System.IdentityModel.Tokens.Jwt](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet) | nuget | minor | `6.29.0` -> `6.30.0` | --- ### Release Notes <details> <summary>AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet</summary> ### [`v6.30.0`](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/releases/tag/6.30.0): April release with new API and bug fixes (6.30.0) [Compare Source](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/compare/6.29.0...6.30.0) Beginning in release [6.28.0](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/releases/tag/6.28.0) the library stopped throwing SecurityTokenUnableToValidateException. This version (6.30.0) marks the exception type as obsolete to make this change more discoverable. Not including it in the release notes explicitly for 6.28.0 was a mistake. This exception type will be removed completely in the next few months as the team moves towards a major version bump. More information on how to replace the usage going forward can be found here: https://aka.ms/SecurityTokenUnableToValidateException Indicate that a SecurityTokenDescriptor can create JWS or JWE [https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2055](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2055) Specify 'UTC' in log messages AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet@ceb10b1 Fix order of log messages AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet@05eeeb5 Fixed issues with matching Jwt.Kid with a X509SecurityKey.x5t [https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2057](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2057) [https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2061](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2061) Marked Exception that is no longer used as obsolete [https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2060](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2060) Added support for AesGcm on .NET 6.0 or higher AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet@85fa86a First round of triming analysis preperation for AOT [https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2042](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2042) Added new API on TokenHandler.ValidateTokenAsync(SecurityToken ...) implemented only on JsonWebTokenHandler. [https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2056](https://togithub.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/2056) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "after 10pm every weekday,every weekend,before 5am every weekday" in timezone Europe/Berlin, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/orso-co/Orso.Arpa.Api). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS42My4xIiwidXBkYXRlZEluVmVyIjoiMzUuNjMuMSJ9--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
](https://renovatebot.com){kind=link}
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.
An issuer signing key is resolved using the values of KeyId or X5t (of a X509SecurityKey) of a signing key. However, for a X509SecurityKey, the X5t value is not being compared consistently in the JwtTokenUtilities.ResolveTokenSigningKey() method. For example, the method checks if the validationParameters.IssuerSigningKey is a X509SecurityKey and compares the X5t value if it is, but the same logic is not applied to the validationParameters.IssuerSigningKeys.
The changes are meant to ensure consistency and reduce the number of places where values are compared.