search

Basis-Theory / azure-keyvault-emulator

https://basistheory.com
Apache License 2.0
31 stars 4 forks source link

chore(deps): bump Microsoft.IdentityModel.Tokens from 6.23.1 to 6.30.0 #126

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps Microsoft.IdentityModel.Tokens from 6.23.1 to 6.30.0.

Release notes

Sourced from Microsoft.IdentityModel.Tokens's releases.

April release with new API and bug fixes (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 https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/commit/ceb10b10ad2edb97217e263915d407da1d957e03 Fix order of log messages https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/commit/05eeeb513e66a4236ae519ef9304bf2b6f26766f

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 https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/commit/85fa86af743e2b1a0078a9ecd956f34ee703acfc

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

6.28.0

6.27.0

Servicing release Set maximum depth for Newtonsoft parsing. AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#2024 Improve metadata failure message. AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#2010 Validate size of symmetric signatures. AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#2008 Added property TokenEndpoint to BaseConfiguration.

... (truncated)

Changelog

Sourced from Microsoft.IdentityModel.Tokens'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
  • 2a1cf33 Resolve a signing key using both KeyId and X5t in a consistent manner (#2061)
  • 3db0e02 Mark SecurityTokenUnableToValidateException as obsolete with guidance (#2060)
  • 3d91c43 Need to check for 'null-or-empty' issuer signing keys (#2057)
  • ceb10b1 Make more time related validation related error messages more user-friendly
  • 3923b62 Update XML documentation of JsonWebTokenHandler.CreateToken(SecurityTokenDesc...
  • b2375cb added the new ValidateTokenAsync(JsonWebToken jsonWebToken, TokenValidationPa...
  • bf27057 Updating buildConfiguration.xml version to the next release version
  • 85fa86a Add support for AesGcm.IsSupported on .NET 6.0 and higher
  • e65930f First Round of Trimming Analysis
  • 05eeeb5 fix order of log parameter according to log message
  • Additional commits viewable in compare view


Dependabot compatibility score

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[bot] commented 1 year ago

Superseded by #127.