chore(deps): Bump System.IdentityModel.Tokens.Jwt from 6.25.0 to 6.31.0

[dependabot]

Bumps System.IdentityModel.Tokens.Jwt from 6.25.0 to 6.31.0.

Release notes

Sourced from System.IdentityModel.Tokens.Jwt's releases.

6.31.0

This release contains work from the following PRs and commits:

• Introduce ConfigurationValidationException(#2076)
• Disarm security artifacts(#2064)
• Throw SecurityTokenMalformedTokenException on malformed tokens(#2080)
• Add ClaimsMapping to JsonWebTokenHandler AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet@8e7f07e

6.30.1

This release contains work from the following PRs:

• Modified token validation to be async throughout the call graph #2075
• Enforce key sizes when creating HMAC #2072
• Fix AotCompatibilityTests #2066
• Use up-to-date "now", in case take long time to get Metadata #2063

This release addresses #1743 and, as such, going forward if the SymmetricKey is smaller than the required size for HMAC IdentityModel will throw an ArgumentOutOfRangeException which is the same exception when the SymmetricKey is smaller than the minimum key size for encryption.

6.30.0

Beginning in release 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 AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#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 AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#2057 AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#2061

Marked Exception that is no longer used as obsolete AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#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 AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#2042

Added new API on TokenHandler.ValidateTokenAsync(SecurityToken ...) implemented only on JsonWebTokenHandler. AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#2056

6.29.0

• Add BootstrapRefreshInterval (#2052)
• Added net462 target (#2049)
• Create the configuration cache in the BaseConfigurationManager class (#2048)

6.28.1

... (truncated)

Changelog

Sourced from System.IdentityModel.Tokens.Jwt's changelog.

See the releases for details on bug fixes and added features.

6.26.1

Bug Fixes:

Releasing a Hotfix for Wilson 6.26.0 that reverts async/await changes made in #1996 to address a performance reduction issue.

• Changes are in #2015
• Root cause analysis and fix will be tracked in #2017

Next release (6.22.1 or 6.23.0)

New Features:

Microsoft.IdentityModel has two assemblies to manipulate JWT tokens:

System.IdentityModel.Tokens.Jwt, which is the legacy assembly. It defines JwtSecurityTokenHandler class to manipulate JWT tokens. Microsoft.IdentityModel.JsonWebTokens, which defines the JsonWebToken class and JsonWebTokenHandler, more modern, and more efficient. When using JwtSecurityTokenHandler, the short named claims (oid, tid), used to be transformed into the long named claims (with a namespace). With JsonWebTokenHandler this is no longer the case, but when you migrate your application from using JwtSecurityTokenHandler to JsonWebTokenHandler (or use a framework that does), you will only get original claims sent by the IdP. This is more efficient, and occupies less space, but might trigger a lot of changes in your application. In order to make it easier for people to migrate without changing their app too much, this PR offers extensibility to re-add the claims mapping.

Bug Fixes:

6.22.0

New Features:

Unmasked non-PII properties in log messages - In Microsoft.IdentityModel logs, previously only system metadata (DateTime, class name, httpmethod etc.) was displayed in clear text. For all other log arguments, the type was being logged to prevent Personally Identifiable Information (PII) from being displayed when ShowPII flag is turned OFF. To improve troubleshooting experience non-PII properties - Issuer, Audience, Key location, Key Id (kid) and some SAML constants will now be displayed in clear text. See issue #1903 for more details.

Prefix Wilson header message to the first log message - To always log the Wilson header (Version, DateTime, PII ON/OFF message), EventLogLevel.LogAlways was mapped to LogLevel.Critical in Microsoft.IdentityModel.LoggingExtensions.IdentityLoggerAdapter class which caused confusion on why header was being displayed as a fatal log. To address this, header is now prefixed to the first message logged by Wilson and separated with a newline. EventLogLevel.LogAlways has been remapped to LogLevel.Trace. See issue #1907 for more details.

Bug Fixes:

Copy the IssuerSigningKeyResolverUsingConfiguration delegate in Clone() #1909

Commits

• 0ac187f Update AotCompatibilityTests.cs
• 48aab10 Introduce ConfigurationValidationException (#2076)
• 5f742de Xiao/DisarmSecurityArtifact (#2064)
• 764f88d Throws SecurityTokenMalformedTokenException on malformed tokens (#2080)
• 8e7f07e Add ClaimsMapping to JsonWebTokenHandler
• 02518f7 Re-enable EnsureAotCompatibility test
• 2b1b78b Update patch version to 6.30.2 (#2077)
• 2468413 modified token validation to be async throughout the call graph
• 25545cd created helper method for validating key sizes
• 008e2f7 Enforce key sizes when creating HMAC
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #524.