dependabot[bot] opened a new pull request, #69:
URL: https://github.com/apache/fineract-loan-origination/pull/69

   Bumps [io.jsonwebtoken:jjwt-impl](https://github.com/jwtk/jjwt) from 0.12.6 
to 0.13.0.
   <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.13.0</h2>
   <p><strong>This is the last minor JJWT release branch that will support Java 
7</strong>.</p>
   <p>Any necessary emergency bug fixes will be fixed in subsequent 
<code>0.13.x</code> patch releases, but all new development, including <a 
href="https://github.com/jwtk/jjwt/issues?q=is%3Aissue%20label%3Ajdk8";>Java 8 
compatible changes</a>, will be in the next minor (<code>0.14.0</code>) 
release.</p>
   <p><strong>All future JJWT major and minor versions (  <code>0.14.0</code> 
and later) will require Java 8 or later.</strong></p>
   <h2>What's Changed</h2>
   <p>This release contains a single change:</p>
   <ul>
   <li>The previously private <code>JacksonDeserializer(ObjectMapper 
objectMapper, Map&lt;String, Class&lt;?&gt;&gt; claimTypeMap)</code> 
constructor is now <code>public</code> for those that want register a claims  
type converter on their own specified <code>ObjectMapper</code> instance. Thank 
you to <a 
href="https://github.com/kesrishubham2510";><code>@​kesrishubham2510</code></a> 
for PR <a href="https://redirect.github.com/jwtk/jjwt/issues/972";>#972</a>. See 
<a href="https://redirect.github.com/jwtk/jjwt/issues/914";>Issue 914</a>.</li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/jwtk/jjwt/compare/0.12.7...0.13.0";>https://github.com/jwtk/jjwt/compare/0.12.7...0.13.0</a></p>
   <h2>0.12.7</h2>
   <p>This patch release:</p>
   <ul>
   <li>
   <p>Adds a new Maven BOM! This is useful for multi-module projects. See <a 
href="https://redirect.github.com/jwtk/jjwt/issues/967";>Issue 967</a>.</p>
   </li>
   <li>
   <p>Allows the <code>JwtParserBuilder</code> to have empty nested algorithm 
collections, effectively disabling the parser's associated feature:</p>
   <ul>
   <li>Emptying the <code>zip()</code> nested collection disables JWT 
decompression.</li>
   <li>Emptying the <code>sig()</code> nested collection disables JWS 
mac/signature verification (i.e. all JWSs will be unsupported/rejected).</li>
   <li>Emptying either the <code>enc()</code> or <code>key()</code> nested 
collections disables JWE decryption (i.e. all JWEs will be 
unsupported/rejected)</li>
   </ul>
   <p>See <a href="https://redirect.github.com/jwtk/jjwt/issues/996";>Issue 
996</a>.</p>
   </li>
   <li>
   <p>Fixes <a href="https://redirect.github.com/jwtk/jjwt/issues/961";>bug 
961</a> where <code>JwtParserBuilder</code> nested collection builders were not 
correctly replacing algorithms with the same id.</p>
   </li>
   <li>
   <p>Ensures a <code>JwkSet</code>'s <code>keys</code> collection is no longer 
entirely secret/redacted by default.  This was an overzealous default that was 
unnecessarily restrictive; the <code>keys</code> collection itself should 
always be public, and each individual key within should determine which fields 
should be redacted when printed. See <a 
href="https://redirect.github.com/jwtk/jjwt/issues/976";>Issue 976</a>.</p>
   </li>
   <li>
   <p>Improves performance slightly by ensuring all <code>jjwt-api</code> 
utility methods that create <code>*Builder</code> instances 
(<code>Jwts.builder()</code>, <code>Jwts.parserBuilder()</code>, 
<code>Jwks.builder()</code>, etc) no longer use reflection.</p>
   <p>Instead,<code>static</code> factories are created via reflection only 
once during initial <code>jjwt-api</code> classloading, and then 
<code>*Builder</code>s are created via standard instantiation using the 
<code>new</code> operator thereafter.  This also benefits certain environments 
that may not have ideal <code>ClassLoader</code> implementations (e.g. Tomcat 
in some cases).</p>
   <p><strong>NOTE: because this changes which classes are loaded via 
reflection, any environments that must explicitly reference reflective class 
names (e.g. GraalVM applications) will need to be updated to reflect the new 
factory class names</strong>.</p>
   <p>See <a href="https://redirect.github.com/jwtk/jjwt/issues/988";>Issue 
988</a>.</p>
   </li>
   <li>
   <p>Upgrades the Gson dependency to <code>2.11.0</code></p>
   </li>
   <li>
   <p>Upgrades the BouncyCastle dependency to <code>1.78.1</code></p>
   </li>
   </ul>
   <h2>New Contributors</h2>
   <ul>
   <li><a href="https://github.com/sigpwned";><code>@​sigpwned</code></a> made 
their first contribution in <a 
href="https://redirect.github.com/jwtk/jjwt/pull/968";>jwtk/jjwt#968</a></li>
   <li><a 
href="https://github.com/TheMrMilchmann";><code>@​TheMrMilchmann</code></a> made 
their first contribution in <a 
href="https://redirect.github.com/jwtk/jjwt/pull/979";>jwtk/jjwt#979</a></li>
   <li><a href="https://github.com/atanasg";><code>@​atanasg</code></a> made 
their first contribution in <a 
href="https://redirect.github.com/jwtk/jjwt/pull/974";>jwtk/jjwt#974</a></li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/jwtk/jjwt/compare/0.12.6...0.12.7";>https://github.com/jwtk/jjwt/compare/0.12.6...0.12.7</a></p>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/jwtk/jjwt/blob/main/CHANGELOG.md";>io.jsonwebtoken:jjwt-impl's
 changelog</a>.</em></p>
   <blockquote>
   <h3>0.13.0</h3>
   <p>This is the last minor JJWT release branch that will support Java 7. Any 
necessary emergency bug fixes will be fixed in subsequent <code>0.13.x</code> 
patch releases, but all new development, including Java 8 compatible changes, 
will be in the next minor (<code>0.14.0</code>) release.</p>
   <p><strong>All future JJWT major and minor versions (  <code>0.14.0</code> 
and later) will require Java 8 or later.</strong></p>
   <p>This <code>0.13.0</code> minor release has only one change:</p>
   <ul>
   <li>The previously private <code>JacksonDeserializer(ObjectMapper 
objectMapper, Map&lt;String, Class&lt;?&gt;&gt; claimTypeMap)</code> 
constructor is now <code>public</code> for those that want register a claims
   type converter on their own specified <code>ObjectMapper</code> instance.  
See <a href="https://redirect.github.com/jwtk/jjwt/issues/914";>Issue 
914</a>.</li>
   </ul>
   <h3>0.12.7</h3>
   <p>This patch release:</p>
   <ul>
   <li>
   <p>Adds a new Maven BOM, useful for multi-module projects. See <a 
href="https://redirect.github.com/jwtk/jjwt/issues/967";>Issue 967</a>.</p>
   </li>
   <li>
   <p>Allows the <code>JwtParserBuilder</code> to have empty nested algorithm 
collections, effectively disabling the parser's associated feature:</p>
   <ul>
   <li>Emptying the <code>zip()</code> nested collection disables JWT 
decompression.</li>
   <li>Emptying the <code>sig()</code> nested collection disables JWS 
mac/signature verification (i.e. all JWSs will be unsupported/rejected).</li>
   <li>Emptying either the <code>enc()</code> or <code>key()</code> nested 
collections disables JWE decryption (i.e. all JWEs will be 
unsupported/rejected)</li>
   </ul>
   <p>See <a href="https://redirect.github.com/jwtk/jjwt/issues/996";>Issue 
996</a>.</p>
   </li>
   <li>
   <p>Fixes <a href="https://redirect.github.com/jwtk/jjwt/issues/961";>bug 
961</a> where <code>JwtParserBuilder</code> nested collection builders were not 
correctly replacing algorithms with the same id.</p>
   </li>
   <li>
   <p>Ensures a <code>JwkSet</code>'s <code>keys</code> collection is no longer 
entirely secret/redacted by default.  This was an overzealous default that was 
unnecessarily restrictive; the <code>keys</code> collection itself should 
always be public, and each individual key within should determine which fields 
should be redacted when printed. See <a 
href="https://redirect.github.com/jwtk/jjwt/issues/976";>Issue 976</a>.</p>
   </li>
   <li>
   <p>Improves performance slightly by ensuring all <code>jjwt-api</code> 
utility methods that create <code>*Builder</code> instances 
(<code>Jwts.builder()</code>, <code>Jwts.parserBuilder()</code>, 
<code>Jwks.builder()</code>, etc) no longer use reflection.</p>
   <p>Instead,<code>static</code> factories are created via reflection only 
once during initial <code>jjwt-api</code> classloading, and then 
<code>*Builder</code>s are created via standard instantiation using the 
<code>new</code> operator thereafter.  This also benefits certain environments 
that may not have ideal <code>ClassLoader</code> implementations (e.g. Tomcat 
in some cases).</p>
   <p><strong>NOTE: because this changes which classes are loaded via 
reflection, any environments that must explicitly reference reflective class 
names (e.g. GraalVM applications) will need to be updated to reflect the new 
factory class names</strong>.</p>
   <p>See <a href="https://redirect.github.com/jwtk/jjwt/issues/988";>Issue 
988</a>.</p>
   </li>
   <li>
   <p>Upgrades the Gson dependency to <code>2.11.0</code></p>
   </li>
   <li>
   <p>Upgrades the BouncyCastle dependency to <code>1.78.1</code></p>
   </li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/a757addce04f6b6d8086beeee8dafcf670550a5b";><code>a757add</code></a>
 [maven-release-plugin] prepare release 0.13.0</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/e357463c59cf62c1f70503ac0102d10efcdfc37d";><code>e357463</code></a>
 Preparing for the 0.13.0 release.</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/b6f8cb82a9c2e9817d842bfe72d2c8fb03124342";><code>b6f8cb8</code></a>
 Made constructor public to allow users their own objectMapper instance (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/972";>#972</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/03f088a4eb774bae2403c428aa885a12d3afde14";><code>03f088a</code></a>
 Bumping development version to 0.13.0-SNAPSHOT (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/1014";>#1014</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/3f2697f854bedebe63e9eddb8c596f76086d11ca";><code>3f2697f</code></a>
 Release 0.12.7 (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/1012";>#1012</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/efed1cf56f9b9715e60eaac7fda6b2c4b62410b9";><code>efed1cf</code></a>
 Updated 0.12.7 change list</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/ca27b122b7f44f3bdd4cd4f636d084f38cc3b3c8";><code>ca27b12</code></a>
 Resolves <a href="https://redirect.github.com/jwtk/jjwt/issues/1010";>#1010</a> 
(<a href="https://redirect.github.com/jwtk/jjwt/issues/1011";>#1011</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/55c7b9adef88328f59534f232060830c34f25478";><code>55c7b9a</code></a>
 Resolves <a href="https://redirect.github.com/jwtk/jjwt/issues/771";>#771</a> 
(<a href="https://redirect.github.com/jwtk/jjwt/issues/1009";>#1009</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/6e9c6a5a825c5ec38f90006f48cc1f8640a6d82e";><code>6e9c6a5</code></a>
 Bump org.bouncycastle:bcpkix-jdk18on from 1.78 to 1.78.1 (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/1008";>#1008</a>)</li>
   <li><a 
href="https://github.com/jwtk/jjwt/commit/7ec7dd1a19a38a1829903f88b9512697bfb7be3c";><code>7ec7dd1</code></a>
 Enable JwtParser empty nested algorithm collections. (<a 
href="https://redirect.github.com/jwtk/jjwt/issues/1007";>#1007</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/jwtk/jjwt/compare/0.12.6...0.13.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=io.jsonwebtoken:jjwt-impl&package-manager=maven&previous-version=0.12.6&new-version=0.13.0)](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 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