dependabot[bot] opened a new pull request, #2439: URL: https://github.com/apache/streampipes/pull/2439
Bumps `jjwt.version` from 0.11.2 to 0.12.4. Updates `io.jsonwebtoken:jjwt-api` from 0.11.2 to 0.12.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jwtk/jjwt/releases";>io.jsonwebtoken:jjwt-api's releases</a>.</em></p> <blockquote> <h2>0.12.4</h2> <p>This is patch release completes <a href="https://github.com/jwtk/jjwt/issues?q=milestone%3A0.12.4+is%3Aissue";>10 issues</a>, with two especially noteworthy changes, and a number of other smaller bug fixes and enhancements.</p> <ol> <li>The default Jackson deserializer will now reject duplicate JSON members by default in an attempt to be a little more strict at rejecting potentially malicious or malformed JSON. This is a default and can be overridden with a custom <code>ObjectMapper</code> if desired.</li> <li>Password-based JWE encryption key algorithms (<code>PBES2_HS256_A128KW</code>, <code>PBES2_HS384_A192KW</code> and <code>PBES2_HS512_A256KW</code>) now enforce an upper bound (maximum) number of iterations allowed during decryption to mitigate against potential DoS attacks. Many thanks to Jingcheng Yang and Jianjun Chen from Sichuan University and Zhongguancun Lab for their work on this!</li> </ol> <p>A number of other issues fixed: thread-safe <code>ServiceLoader</code> usage for dynamic JSON processor lookup, Android enhancements for JSON <code>Reader</code> APIs, fixed Elliptic Curve field element padding, and more. Please read the <a href="https://github.com/jwtk/jjwt/blob/0.12.4/CHANGELOG.md";>0.12.4 CHANGELOG</a> for full details of all of these changes, and as always, project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.4/README.md";>0.12.4 README</a>.</p> <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p> <h2>0.12.3</h2> <p>This is a minor patch release that address two issues:</p> <ol> <li> <p>The <code>org.json</code> dependency has been upgraded to <code>20231013</code> to address that library's <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5072";>CVE-2023-5072</a> vulnerability.</p> </li> <li> <p>Empty custom claims values are (re-)enabled which was the behavior in <= 0.11.5. See <a href="https://redirect.github.com/jwtk/jjwt/issues/858";>Issue 858</a>.</p> </li> </ol> <p>These same notes are repeated in the <a href="https://github.com/jwtk/jjwt/blob/0.12.3/CHANGELOG.md";>CHANGELOG</a>, and as always, project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.3/README.md";>README</a>.</p> <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p> <h2>0.12.2</h2> <p>This is a follow-up release to finalize the work in <code>0.12.1</code> that tried to fix a reflection scope problem on >= JDK 17. The 0.12.1 fix worked, but only if the importing project or application did <em>not</em> have its own <code>module-info.java</code> file.</p> <p>This release removes that reflection code entirely in favor of a JJWT-native implementation, eliminating JPMS module (scope) problems on >= JDK 17. As such, <code>--add-opens</code> flags are no longer required to use JJWT.</p> <p>The fix has been tested up through JDK 21 in a separate application environment (out of JJWT's codebase) to assert expected functionality in a 'clean room' environment in a project both with and without <code>module-info.java</code> usage.</p> <p>Notes are in the <a href="https://github.com/jwtk/jjwt/blob/0.12.2/CHANGELOG.md";>CHANGELOG</a>, and project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.2/README.md";>README</a>.</p> <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p> <h2>0.12.1</h2> <p>This is a quick follow-up release from yesterday's <code>0.12.0</code> release that addresses a reflection issue on JDK 17. The fix has been tested up through JDK 21.</p> <p>Notes are in the <a href="https://github.com/jwtk/jjwt/blob/0.12.1/CHANGELOG.md";>CHANGELOG</a>, and project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.1/README.md";>README</a>.</p> <p>Please allow 30 minutes for the release to be available in Maven Central.</p> <h2>0.12.0</h2> <p>It is finally here! This release includes full support for JSON Web Encryption (JWE), JSON Web Keys (JWK), JSON Web Key Thumbprints, JSON Web Key Thumbprint URIs, and so, so much more.</p> <p>This is the culmination of <em>hundreds</em> of hours worth of work and testing, and we're glad to <em>finally</em> release it. However, please note:</p> <p><strong>This is our first-ever breaking change release.</strong> While we tried hard to minimize the breakages, some were just necessary in preparation for 1.0 and to finalize all JWT RFC features. <strong>If you are not partial to fixing changes when upgrading a library, we strongly encourage you to wait until the 1.0 release.</strong></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jwtk/jjwt/blob/master/CHANGELOG.md";>io.jsonwebtoken:jjwt-api's changelog</a>.</em></p> <blockquote> <h3>0.12.4</h3> <p>This patch release includes various changes listed below.</p> <h4>Jackson Default Parsing Behavior</h4> <p>This release makes two behavioral changes to JJWT's default Jackson <code>ObjectMapper</code> parsing settings:</p> <ol> <li> <p>In the interest of having stronger standards to reject potentially malformed/malicious/accidental JSON that could have undesirable effects on an application, JJWT's default <code>ObjectMapper </code>is now configured to explicitly reject/fail parsing JSON (JWT headers and/or Claims) if/when that JSON contains duplicate JSON member names.</p> <p>For example, now the following JSON, if parsed, would fail (be rejected) by default:</p> <pre lang="json"><code>{ "hello": "world", "thisWillFail": 42, "thisWillFail": "test" } </code></pre> <p>Technically, the JWT RFCs <em>do allow</em> duplicate named fields as long as the last parsed member is the one used (see <a href="https://datatracker.ietf.org/doc/html/rfc7515#section-4";>JWS RFC 7515, Section 4</a>), so this is allowed. However, because JWTs often reflect security concepts, it's usually better to be defensive and reject these unexpected scenarios by default. The RFC later supports this position/preference in <a href="https://datatracker.ietf.org/doc/html/rfc7515#section-10.12";>Section 10.12</a>:</p> <pre><code>Ambiguous and potentially exploitable situations could arise if the JSON parser used does not enforce the uniqueness of member names or returns an unpredictable value for duplicate member names. </code></pre> <p>Finally, this is just a default, and the RFC does indeed allow duplicate member names if the last value is used, so applications that require duplicates to be allowed can simply configure their own <code>ObjectMapper</code> and use that with JJWT instead of assuming this (new) JJWT default. See [Issue <a href="https://redirect.github.com/jwtk/jjwt/issues/877";>#877</a>](<a href="https://redirect.github.com/jwtk/jjwt/issues/877";>jwtk/jjwt#877</a>) for more.</p> </li> <li> <p>If using JJWT's support to use Jackson to parse <a href="https://github.com/jwtk/jjwt#json-jackson-custom-types";>Custom Claim Types</a> (for example, a Claim that should be unmarshalled into a POJO), and the JSON for that POJO contained a member that is not represented in the specified class, Jackson would fail parsing by default. Because POJOs and JSON data models can sometimes be out of sync due to different class versions, the default behavior has been changed to ignore these unknown JSON members instead of failing (i.e. the <code>ObjectMapper</code>'s <code>DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES</code> is now set to <code>false</code>) by default.</p> <p>Again, if you prefer the stricter behavior of rejecting JSON with extra or unknown properties, you can configure <code>true</code> on your own <code>ObjectMapper</code> instance and use that instance with the <code>Jwts.parser()</code> builder.</p> </li> </ol> <h4>Additional Changes</h4> <p>This release also:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jwtk/jjwt/commit/bf4168cdceb85435b17d912a2087960ae597d37f";><code>bf4168c</code></a> [maven-release-plugin] prepare release 0.12.4</li> <li><a href="https://github.com/jwtk/jjwt/commit/5c6dec061ff99ef7122a33960ada95e496a37087";><code>5c6dec0</code></a> - Adding 0.12.4 release version references</li> <li><a href="https://github.com/jwtk/jjwt/commit/dd10b12b53b5bb26299c5435aa9d193e71b6b918";><code>dd10b12</code></a> Added JWK Set documentation to README.mdJwkset doc (<a href="https://redirect.github.com/jwtk/jjwt/issues/912";>#912</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/6335381c978ce83c9c15bd3c349f32d1bed72d4f";><code>6335381</code></a> PBES2 decryption maximum iterations (<a href="https://redirect.github.com/jwtk/jjwt/issues/911";>#911</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/2884eb79529ec8b56ecdd7c9f7e7fbea5dfc4806";><code>2884eb7</code></a> - Updating to GitHub latest actions/checkout and actions/setup-java script ve...</li> <li><a href="https://github.com/jwtk/jjwt/commit/628bd6f4e8b885be2f9cfbd8cbf0767ce616003a";><code>628bd6f</code></a> Secret JWK <code>k</code> values larger than HMAC-SHA minimums (<a href="https://redirect.github.com/jwtk/jjwt/issues/909";>#909</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/b12dabf100bbe8749d9bce49628d70b9f73af729";><code>b12dabf</code></a> Fix small typos (<a href="https://redirect.github.com/jwtk/jjwt/issues/908";>#908</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/26f5dc3dbbb6070735498e4ea497f174b0a3850f";><code>26f5dc3</code></a> Updating changelog with more information/clarity for the 0.12.4 release (<a href="https://redirect.github.com/jwtk/jjwt/issues/907";>#907</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/f61cfa875d1bfd9164c16069ab62bf7b74fcc831";><code>f61cfa8</code></a> Test case change to reflect accurate assertion for Elliptic Curve 'd' values ...</li> <li><a href="https://github.com/jwtk/jjwt/commit/fd619e0a4229e01cbd3ab1bd0a7a4f6cab21d784";><code>fd619e0</code></a> disable FAIL_ON_UNKNOWN_PROPERTIES deserialization feature of Jackson by defa...</li> <li>Additional commits viewable in <a href="https://github.com/jwtk/jjwt/compare/0.11.2...0.12.4";>compare view</a></li> </ul> </details> <br /> Updates `io.jsonwebtoken:jjwt-impl` from 0.11.2 to 0.12.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jwtk/jjwt/releases";>io.jsonwebtoken:jjwt-impl's releases</a>.</em></p> <blockquote> <h2>0.12.4</h2> <p>This is patch release completes <a href="https://github.com/jwtk/jjwt/issues?q=milestone%3A0.12.4+is%3Aissue";>10 issues</a>, with two especially noteworthy changes, and a number of other smaller bug fixes and enhancements.</p> <ol> <li>The default Jackson deserializer will now reject duplicate JSON members by default in an attempt to be a little more strict at rejecting potentially malicious or malformed JSON. This is a default and can be overridden with a custom <code>ObjectMapper</code> if desired.</li> <li>Password-based JWE encryption key algorithms (<code>PBES2_HS256_A128KW</code>, <code>PBES2_HS384_A192KW</code> and <code>PBES2_HS512_A256KW</code>) now enforce an upper bound (maximum) number of iterations allowed during decryption to mitigate against potential DoS attacks. Many thanks to Jingcheng Yang and Jianjun Chen from Sichuan University and Zhongguancun Lab for their work on this!</li> </ol> <p>A number of other issues fixed: thread-safe <code>ServiceLoader</code> usage for dynamic JSON processor lookup, Android enhancements for JSON <code>Reader</code> APIs, fixed Elliptic Curve field element padding, and more. Please read the <a href="https://github.com/jwtk/jjwt/blob/0.12.4/CHANGELOG.md";>0.12.4 CHANGELOG</a> for full details of all of these changes, and as always, project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.4/README.md";>0.12.4 README</a>.</p> <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p> <h2>0.12.3</h2> <p>This is a minor patch release that address two issues:</p> <ol> <li> <p>The <code>org.json</code> dependency has been upgraded to <code>20231013</code> to address that library's <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-5072";>CVE-2023-5072</a> vulnerability.</p> </li> <li> <p>Empty custom claims values are (re-)enabled which was the behavior in <= 0.11.5. See <a href="https://redirect.github.com/jwtk/jjwt/issues/858";>Issue 858</a>.</p> </li> </ol> <p>These same notes are repeated in the <a href="https://github.com/jwtk/jjwt/blob/0.12.3/CHANGELOG.md";>CHANGELOG</a>, and as always, project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.3/README.md";>README</a>.</p> <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p> <h2>0.12.2</h2> <p>This is a follow-up release to finalize the work in <code>0.12.1</code> that tried to fix a reflection scope problem on >= JDK 17. The 0.12.1 fix worked, but only if the importing project or application did <em>not</em> have its own <code>module-info.java</code> file.</p> <p>This release removes that reflection code entirely in favor of a JJWT-native implementation, eliminating JPMS module (scope) problems on >= JDK 17. As such, <code>--add-opens</code> flags are no longer required to use JJWT.</p> <p>The fix has been tested up through JDK 21 in a separate application environment (out of JJWT's codebase) to assert expected functionality in a 'clean room' environment in a project both with and without <code>module-info.java</code> usage.</p> <p>Notes are in the <a href="https://github.com/jwtk/jjwt/blob/0.12.2/CHANGELOG.md";>CHANGELOG</a>, and project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.2/README.md";>README</a>.</p> <p>Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.</p> <h2>0.12.1</h2> <p>This is a quick follow-up release from yesterday's <code>0.12.0</code> release that addresses a reflection issue on JDK 17. The fix has been tested up through JDK 21.</p> <p>Notes are in the <a href="https://github.com/jwtk/jjwt/blob/0.12.1/CHANGELOG.md";>CHANGELOG</a>, and project documentation is in the <a href="https://github.com/jwtk/jjwt/blob/0.12.1/README.md";>README</a>.</p> <p>Please allow 30 minutes for the release to be available in Maven Central.</p> <h2>0.12.0</h2> <p>It is finally here! This release includes full support for JSON Web Encryption (JWE), JSON Web Keys (JWK), JSON Web Key Thumbprints, JSON Web Key Thumbprint URIs, and so, so much more.</p> <p>This is the culmination of <em>hundreds</em> of hours worth of work and testing, and we're glad to <em>finally</em> release it. However, please note:</p> <p><strong>This is our first-ever breaking change release.</strong> While we tried hard to minimize the breakages, some were just necessary in preparation for 1.0 and to finalize all JWT RFC features. <strong>If you are not partial to fixing changes when upgrading a library, we strongly encourage you to wait until the 1.0 release.</strong></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jwtk/jjwt/blob/master/CHANGELOG.md";>io.jsonwebtoken:jjwt-impl's changelog</a>.</em></p> <blockquote> <h3>0.12.4</h3> <p>This patch release includes various changes listed below.</p> <h4>Jackson Default Parsing Behavior</h4> <p>This release makes two behavioral changes to JJWT's default Jackson <code>ObjectMapper</code> parsing settings:</p> <ol> <li> <p>In the interest of having stronger standards to reject potentially malformed/malicious/accidental JSON that could have undesirable effects on an application, JJWT's default <code>ObjectMapper </code>is now configured to explicitly reject/fail parsing JSON (JWT headers and/or Claims) if/when that JSON contains duplicate JSON member names.</p> <p>For example, now the following JSON, if parsed, would fail (be rejected) by default:</p> <pre lang="json"><code>{ "hello": "world", "thisWillFail": 42, "thisWillFail": "test" } </code></pre> <p>Technically, the JWT RFCs <em>do allow</em> duplicate named fields as long as the last parsed member is the one used (see <a href="https://datatracker.ietf.org/doc/html/rfc7515#section-4";>JWS RFC 7515, Section 4</a>), so this is allowed. However, because JWTs often reflect security concepts, it's usually better to be defensive and reject these unexpected scenarios by default. The RFC later supports this position/preference in <a href="https://datatracker.ietf.org/doc/html/rfc7515#section-10.12";>Section 10.12</a>:</p> <pre><code>Ambiguous and potentially exploitable situations could arise if the JSON parser used does not enforce the uniqueness of member names or returns an unpredictable value for duplicate member names. </code></pre> <p>Finally, this is just a default, and the RFC does indeed allow duplicate member names if the last value is used, so applications that require duplicates to be allowed can simply configure their own <code>ObjectMapper</code> and use that with JJWT instead of assuming this (new) JJWT default. See [Issue <a href="https://redirect.github.com/jwtk/jjwt/issues/877";>#877</a>](<a href="https://redirect.github.com/jwtk/jjwt/issues/877";>jwtk/jjwt#877</a>) for more.</p> </li> <li> <p>If using JJWT's support to use Jackson to parse <a href="https://github.com/jwtk/jjwt#json-jackson-custom-types";>Custom Claim Types</a> (for example, a Claim that should be unmarshalled into a POJO), and the JSON for that POJO contained a member that is not represented in the specified class, Jackson would fail parsing by default. Because POJOs and JSON data models can sometimes be out of sync due to different class versions, the default behavior has been changed to ignore these unknown JSON members instead of failing (i.e. the <code>ObjectMapper</code>'s <code>DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES</code> is now set to <code>false</code>) by default.</p> <p>Again, if you prefer the stricter behavior of rejecting JSON with extra or unknown properties, you can configure <code>true</code> on your own <code>ObjectMapper</code> instance and use that instance with the <code>Jwts.parser()</code> builder.</p> </li> </ol> <h4>Additional Changes</h4> <p>This release also:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jwtk/jjwt/commit/bf4168cdceb85435b17d912a2087960ae597d37f";><code>bf4168c</code></a> [maven-release-plugin] prepare release 0.12.4</li> <li><a href="https://github.com/jwtk/jjwt/commit/5c6dec061ff99ef7122a33960ada95e496a37087";><code>5c6dec0</code></a> - Adding 0.12.4 release version references</li> <li><a href="https://github.com/jwtk/jjwt/commit/dd10b12b53b5bb26299c5435aa9d193e71b6b918";><code>dd10b12</code></a> Added JWK Set documentation to README.mdJwkset doc (<a href="https://redirect.github.com/jwtk/jjwt/issues/912";>#912</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/6335381c978ce83c9c15bd3c349f32d1bed72d4f";><code>6335381</code></a> PBES2 decryption maximum iterations (<a href="https://redirect.github.com/jwtk/jjwt/issues/911";>#911</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/2884eb79529ec8b56ecdd7c9f7e7fbea5dfc4806";><code>2884eb7</code></a> - Updating to GitHub latest actions/checkout and actions/setup-java script ve...</li> <li><a href="https://github.com/jwtk/jjwt/commit/628bd6f4e8b885be2f9cfbd8cbf0767ce616003a";><code>628bd6f</code></a> Secret JWK <code>k</code> values larger than HMAC-SHA minimums (<a href="https://redirect.github.com/jwtk/jjwt/issues/909";>#909</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/b12dabf100bbe8749d9bce49628d70b9f73af729";><code>b12dabf</code></a> Fix small typos (<a href="https://redirect.github.com/jwtk/jjwt/issues/908";>#908</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/26f5dc3dbbb6070735498e4ea497f174b0a3850f";><code>26f5dc3</code></a> Updating changelog with more information/clarity for the 0.12.4 release (<a href="https://redirect.github.com/jwtk/jjwt/issues/907";>#907</a>)</li> <li><a href="https://github.com/jwtk/jjwt/commit/f61cfa875d1bfd9164c16069ab62bf7b74fcc831";><code>f61cfa8</code></a> Test case change to reflect accurate assertion for Elliptic Curve 'd' values ...</li> <li><a href="https://github.com/jwtk/jjwt/commit/fd619e0a4229e01cbd3ab1bd0a7a4f6cab21d784";><code>fd619e0</code></a> disable FAIL_ON_UNKNOWN_PROPERTIES deserialization feature of Jackson by defa...</li> <li>Additional commits viewable in <a href="https://github.com/jwtk/jjwt/compare/0.11.2...0.12.4";>compare view</a></li> </ul> </details> <br /> Updates `io.jsonwebtoken:jjwt-jackson` from 0.11.2 to 0.12.4 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@streampipes.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
