dependabot[bot] opened a new pull request, #9451: URL: https://github.com/apache/camel-quarkus/pull/9451
Bumps [com.unboundid:unboundid-ldapsdk](https://github.com/pingidentity/ldapsdk) from 7.0.5 to 7.0.6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pingidentity/ldapsdk/releases";>com.unboundid:unboundid-ldapsdk's releases</a>.</em></p> <blockquote> <h2>UnboundID LDAP SDK for Java 7.0.6</h2> <p>We have just released version 7.0.6 of the <a href="https://github.com/pingidentity/ldapsdk";>UnboundID LDAP SDK for Java</a>. It is available for download from <a href="https://github.com/pingidentity/ldapsdk/releases";>GitHub</a> and <a href="https://sourceforge.net/projects/ldap-sdk/files/";>SourceForge</a>, and it is available in the <a href="https://central.sonatype.com/artifact/com.unboundid/unboundid-ldapsdk/7.0.6";>Maven Central Repository</a>. You can find the release notes for this release (and all previous versions) at <a href="https://docs.ldap.com/ldap-sdk/docs/release-notes.html";>https://docs.ldap.com/ldap-sdk/docs/release-notes.html</a>, but here’s a summary of the changes:</p> <ul> <li> <p>We improved the logic used by the <code>Attribute.nameIsValid</code> methods. These methods are used to determine whether a given string represents a valid attribute description, which include an attribute type name or OID and an optional set of attribute options. Previously, this method could incorrectly reject names with valid attribute options (those starting with digits or a hyphen), and it also didn’t support attributes identified by a numeric OID.</p> </li> <li> <p>We added an <code>Attribute.baseNameIsValid</code> method, which can be used to determine whether a given string represents a valid attribute type name or numeric OID.</p> </li> <li> <p>We added an <code>Attribute.optionNameIsValid</code> method, which can be used to determine whether a given string represents a valid attribute option name.</p> </li> <li> <p>We added a <code>VerifyChainSignaturesTrustManager</code> class, which can be used to verify the signatures in a presented certificate chain. This trust manager expects the end-entity certificate to be the first certificate in the chain, and it ensures that it’s possible to build a trust path using the other provided certificates. For the sake of leniency and compatibility with other implementations, if a certificate is present multiple times in the chain, then the duplicates are ignored, and we also don’t require subsequent certificates in the chain to be presented in the correct order.</p> </li> <li> <p>We permanently disabled auto-reconnect functionality for LDAP connections. This ability had been officially deprecated for over ten years, as it was very fragile and could only work in a limited set of circumstances. The associated methods are still in place to preserve API compatibility, but attempting to enable auto-reconnect no longer has any effect. In cases where you want to use automatic retry functionality, use an LDAP connection pool instead of an individual connection, and use the <code>setRetryFailedOperationsDueToInvalidConnections</code> method to indicate that operations should be retried on a newly established connection if it fails in a way that may indicate that the existing connection is no longer valid.</p> </li> <li> <p>We updated the <code>collect-support-data</code> command-line tool, extended request, and administrative task to add an option to exclude Java Flight Recorder (JFR) ata from the resulting archive. This may be useful in cases where collect-support-data should run as quickly as possible, or should generate a smaller archive file.</p> </li> <li> <p>We updated the <code>BouncyCastleFIPSHelper</code> class to add a couple of constants to make it easier to use the LDAP SDK in conjunction with bc-fips version 2.1.3. This library introduced attempts to use certain native CPU instructions, but that seems to adversely affect reliability on certain platforms.</p> </li> <li> <p>We updated the documentation to include the latest versions of the draft-codere-ldapsyntax, draft-housley-asn1-layman-guide, draft-ietf-kitten-password-storage, draft-ietf-kitten-sasl-ht, and draft-melnikov-sasl2 drafts.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pingidentity/ldapsdk/blob/master/docs/release-notes.html";>com.unboundid:unboundid-ldapsdk's changelog</a>.</em></p> <blockquote> <pre><code> <div align="right"> </code></pre> <p>${TARGET="offline"} <!-- raw HTML omitted -->LDAP SDK Home Page<!-- raw HTML omitted --> ${TARGET="offline"} <!-- raw HTML omitted --> <!-- raw HTML omitted -->Product Information<!-- raw HTML omitted --> <!-- raw HTML omitted --></p> <pre><code> <h2>Release Notes</h2> <pre><code> &lt;h3&gt;Version 7.0.7&lt;/h3&gt; &lt;p&gt; The following changes were made between the 7.0.6 and 7.0.7 releases: &lt;/p&gt; &lt;ul&gt; &lt;li&gt; Updated the documentation to include the latest revisions of draft-housley-asn1-layman-guide and draft-ietf-kitten-scram-2fa in the set of LDAP-related specifications. &lt;br&gt;&lt;br&gt; &lt;/li&gt; &lt;/ul&gt; &lt;p&gt;&lt;/p&gt; &lt;h3&gt;Version 7.0.6&lt;/h3&gt; &lt;p&gt; The following changes were made between the 7.0.5 and 7.0.6 releases: &lt;/p&gt; &lt;ul&gt; &lt;li&gt; Improved the logic used by the Attribute.nameIsValid methods. These methods are used to determine whether a given string represents a valid attribute description, which consists of a base name and zero or more attribute options. Previously, the method incorrectly rejected attribute options whose name started with a digit or a hyphen character, which is a valid initial character for an attribute option, but not for the base attribute name. Further, the method previously only supported textual attribute names, but it now supports numeric OIDs. &lt;br&gt;&lt;br&gt; &lt;/li&gt; &lt;li&gt; Added an Attribute.baseNameIsValid method, which can be used to determine whether a given string represents a valid base attribute type name, optionally allowing for numeric OIDs. </code></pre> <p></code></pre></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pingidentity/ldapsdk/commit/201adff411cb6039f046b0137f4c03229826f814";><code>201adff</code></a> Update LDAP-related specifications</li> <li><a href="https://github.com/pingidentity/ldapsdk/commit/a3439e6a4717b76dc60a84ecc30cc6b6b2014782";><code>a3439e6</code></a> Improve attribute description validation</li> <li><a href="https://github.com/pingidentity/ldapsdk/commit/5fcd858f371170d7d8eaebe7061b282e482c709d";><code>5fcd858</code></a> Update the release note text</li> <li><a href="https://github.com/pingidentity/ldapsdk/commit/46ed343c9736ca1a05d6ffbabdf4caa2019bb89c";><code>46ed343</code></a> Add constants for BC FIPS 2.1.3</li> <li><a href="https://github.com/pingidentity/ldapsdk/commit/3ccde474779363ad7e96524dd3a55447dd2f852d";><code>3ccde47</code></a> Update the OID registry</li> <li><a href="https://github.com/pingidentity/ldapsdk/commit/0d24bc1411e05488fd5a7b8b5f80f25c338dce5b";><code>0d24bc1</code></a> Improve the logic used to allocate message IDs</li> <li><a href="https://github.com/pingidentity/ldapsdk/commit/66e4db97422bbf11f91f2d278c3b9120d049a3d8";><code>66e4db9</code></a> Disable auto-reconnect functionality</li> <li><a href="https://github.com/pingidentity/ldapsdk/commit/cf617ca96a44ccc390773f8bd92addc7406b109c";><code>cf617ca</code></a> Update VerifyChainSignaturesTrustManager</li> <li><a href="https://github.com/pingidentity/ldapsdk/commit/51ba575a0e95221f7cde0746af5ad2bc951b3e93";><code>51ba575</code></a> Add options to exclude JFR data from CSD archives</li> <li><a href="https://github.com/pingidentity/ldapsdk/commit/37d581c166d7d7647571990d3d18333c7d02d970";><code>37d581c</code></a> Add a verify chain signatures trust manager</li> <li>Additional commits viewable in <a href="https://github.com/pingidentity/ldapsdk/compare/7.0.5...7.0.6";>compare view</a></li> </ul> </details> <br /> [](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]
