dependabot[bot] opened a new pull request, #5580:
URL: https://github.com/apache/camel-quarkus/pull/5580

   Bumps 
[com.unboundid:unboundid-ldapsdk](https://github.com/pingidentity/ldapsdk) from 
6.0.10 to 6.0.11.
   <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>          &lt;div align=&quot;right&quot;&gt;
   </code></pre>
   <p>${TARGET=&quot;offline&quot;}                <!-- raw HTML omitted 
-->LDAP SDK Home Page<!-- raw HTML omitted -->
   ${TARGET=&quot;offline&quot;}                <!-- raw HTML omitted -->
   <!-- raw HTML omitted -->Product Information<!-- raw HTML omitted -->
   <!-- raw HTML omitted --></p>
   <pre><code>          &lt;h2&gt;Release Notes&lt;/h2&gt;
   <pre><code>      &amp;lt;h3&amp;gt;Version 6.0.11&amp;lt;/h3&amp;gt;
   
         &amp;lt;p&amp;gt;
           The following changes were made between the 6.0.10 and 6.0.11 
releases:
         &amp;lt;/p&amp;gt;
   
         &amp;lt;ul&amp;gt;
           &amp;lt;li&amp;gt;
             Note that this is the last release that will support Java 7.  The 
next release
             (expected to have a version number of 7.0.0) will only support 
Java 8 and later.
             &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
           &amp;lt;/li&amp;gt;
   
           &amp;lt;li&amp;gt;
             Updated the ldapsearch and ldapmodify command-line tools to 
provide better
             validation for the value of the --proxyAs argument.  The tools 
will now reject
             attempts to use the argument with a value that doesn't start with 
either &amp;quot;dn:&amp;quot; or
             &amp;quot;u:&amp;quot;, and they will also reject attempts to use 
a value that starts with &amp;quot;dn:&amp;quot;
             but is not followed by a valid LDAP DN.
             &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
           &amp;lt;/li&amp;gt;
   
           &amp;lt;li&amp;gt;
             Updated the Filter methods for creating substring filters to 
better support empty
             components.  In LDAP filters, filters are transmitted using a 
binary encoding,
             and substring components may be absent but not empty.  However, 
because
             developers creating LDAP-enabled applications are more likely to 
be familiar with
             the string representations of filters, it is understandable if 
someone were to
             try to provide an empty string instead of null to indicate that 
the component is
             not needed.  The methods for creating substring filters will now 
interpret empty
             components as equivalent to being null, causing them to be omitted 
from the
             resulting encoded LDAP filter.
             &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
           &amp;lt;/li&amp;gt;
   
           &amp;lt;li&amp;gt;
             Updated the logic that the LDAP SDK uses in the in-memory 
directory server and
             the ldifsearch tool to pare matching entries based on a set of 
requested
             attributes in the in-memory.  If an entry included an attribute 
with an invalid
             name, then the logic used to parse an attribute description into 
the base
             attribute type name and a set of attribute options would result in 
a null pointer
             exception.  It now uses more lenient logic for parsing attribute 
descriptions,
   </code></pre>
   <p></code></pre></p>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li>See full diff in <a 
href="https://github.com/pingidentity/ldapsdk/commits";>compare view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.unboundid:unboundid-ldapsdk&package-manager=maven&previous-version=6.0.10&new-version=6.0.11)](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: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to