dependabot[bot] opened a new pull request, #1130:
URL: https://github.com/apache/plc4x/pull/1130

   Bumps [io.jsonwebtoken:jjwt](https://github.com/jwtk/jjwt) from 0.9.1 to 
0.12.1.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/jwtk/jjwt/releases";>io.jsonwebtoken:jjwt's 
releases</a>.</em></p>
   <blockquote>
   <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>
   <p>Please pay particular attention to the <a 
href="https://github.com/jwtk/jjwt/blob/0.12.0/CHANGELOG.md";>CHANGELOG</a> 
listing breaking changes.</p>
   <p>Full documentation is available in the <a 
href="https://github.com/jwtk/jjwt/blob/0.12.0/README.md";>README</a>.</p>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/jwtk/jjwt/blob/master/CHANGELOG.md";>io.jsonwebtoken:jjwt's
 changelog</a>.</em></p>
   <blockquote>
   <h3>0.12.1</h3>
   <p>Enabled reflective access on JDK 17+ to 
<code>java.io.ByteArrayInputStream</code> and 
<code>sun.security.util.KeyUtil</code> for
   <code>jjwt-impl.jar</code></p>
   <h3>0.12.0</h3>
   <p>This is a big release! JJWT now fully supports Encrypted JSON Web Tokens 
(JWE), JSON Web Keys (JWK) and more!  See the
   sections below enumerating all new features as well as important notes on 
breaking changes or backwards-incompatible
   changes made in preparation for the upcoming 1.0 release.</p>
   <p><strong>Because breaking changes are being introduced, it is strongly 
recommended to wait until the upcoming 1.0 release
   where you can address breaking changes one time only</strong>.</p>
   <p>Those that need immediate JWE encryption and JWK key support
   however will likely want to upgrade now and deal with the smaller subset of 
breaking changes in the 1.0 release.</p>
   <h4>Simplified Starter Jar</h4>
   <p>Those upgrading to new modular JJWT versions from old single-jar versions 
will transparently obtain everything
   they need in their Maven, Gradle or Android projects.</p>
   <p>JJWT's early releases had one and only one .jar: <code>jjwt.jar</code>.  
Later releases moved to a modular design with 'api' and
   'impl' jars including 'plugin' jars for Jackson, GSON, org.json, etc.  Some 
users upgrading from the earlier single
   jar to JJWT's later versions have been frustrated by being forced to learn 
how to configure the more modular .jars.</p>
   <p>This release re-introduces the <code>jjwt.jar</code> artifact again, but 
this time it is simply an empty .jar with Maven
   metadata that will automatically transitively download the following into a 
project, retaining the old single-jar
   behavior:</p>
   <ul>
   <li><code>jjwt-api.jar</code></li>
   <li><code>jjwt-impl.jar</code></li>
   <li><code>jjwt-jackson.jar</code></li>
   </ul>
   <p>Naturally, developers are still encouraged to configure the modular .jars 
as described in JJWT's documentation for
   greater control and to enable their preferred JSON parser, but this stop-gap 
should help those unaware when upgrading.</p>
   <h4>JSON Web Encryption (JWE) Support!</h4>
   <p>This has been a long-awaited feature for JJWT, years in the making, and 
it is quite extensive - so many encryption
   algorithms and key management algorithms are defined by the JWA 
specification, and new API concepts had to be
   introduced for all of them, as well as extensive testing with RFC-defined 
test vectors.  The wait is over!<br />
   All JWA-defined encryption algorithms and key management algorithms are 
fully implemented and supported and
   available immediately.  For example:</p>
   <pre lang="java"><code>AeadAlgorithm enc = Jwts.ENC.A256GCM;
   SecretKey key = enc.key().build();
   String compact = Jwts.builder().setSubject(&quot;Joe&quot;).encryptWith(key, 
enc).compact();
   <p>Jwe&lt;Claims&gt; jwe = 
Jwts.parser().decryptWith(key).build().parseEncryptedClaims(compact);
   &lt;/tr&gt;&lt;/table&gt;
   </code></pre></p>
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/15503daa4c35f286708232a831cacd805c47abfc";><code>15503da</code></a>
 [maven-release-plugin] prepare release 0.12.1</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/64b1f0bd1479d37ec1ce56c43a75cbde344e7fd9";><code>64b1f0b</code></a>
 prepping for 0.12.1 release</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/1625067b85680733d275eba86ad46a0d222425a2";><code>1625067</code></a>
 Closes <a href="https://redirect.github.com/jwtk/jjwt/issues/849";>#849</a> (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/852";>#852</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/44cd5523e890c99451682268c7dac951ccd96a18";><code>44cd552</code></a>
 Update README.md</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/0c3040922a43160c071d8e838d9deec51e88f408";><code>0c30409</code></a>
 0.12.0 staging complete (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/847";>#847</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/b411b19b926983e772c0218ebfdd379d79621043";><code>b411b19</code></a>
 key byte array cleanup as necessary (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/846";>#846</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/e78f3f511f0c3ba092a11b414567fdda6f2f8b9b";><code>e78f3f5</code></a>
 JwtParser.parse* method renames (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/845";>#845</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/3b529ac64013396fe2e01fcba482b4d878531cb9";><code>3b529ac</code></a>
 Update maven wrapper</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/05717d0a18da25222e5cf36d2481bdcc6d2f21dc";><code>05717d0</code></a>
 Expanded Parser method argument support (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/844";>#844</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/36a6e1383b6781a6e4fe2e2119a4741489afc4fe";><code>36a6e13</code></a>
 README cleanup based on latest API (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/843";>#843</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/jwtk/jjwt/compare/0.9.1...0.12.1";>compare view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=io.jsonwebtoken:jjwt&package-manager=maven&previous-version=0.9.1&new-version=0.12.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to