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

   Bumps 
[com.unboundid:unboundid-ldapsdk](https://github.com/pingidentity/ldapsdk) from 
6.0.10 to 6.0.11.
   <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 6.0.11</h2>
   <p>We have just released version 6.0.11 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/6.0.11";>Maven
 Central Repository</a>.</p>
   <p>Note that this is the last release of the LDAP SDK that will offer 
support for Java 7. As of the next release (which is expected to have a version 
of 7.0.0), the LDAP SDK will only support Java 8 and later.</p>
   <p>You can find the release notes for the 6.0.11 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 updated the <code>ldapsearch</code> and <code>ldapmodify</code> 
command-line tools to provide better validation for the <code>--proxyAs</code> 
argument, which includes the proxied authorization v2 request control in the 
requests that they issue. Previously, they would accept any string as the 
authorization ID value, but they will verify that it is a valid authorization 
ID using the form “dn:” followed by a valid DN or “u:” followed by a 
username.</p>
   </li>
   <li>
   <p>We updated the <code>Filter</code> class so that the methods used to 
create substring filters are more user-friendly when the filter doesn’t contain 
all types of components. Previously, it expected a substring component to be 
null if that component wasn’t to be included in the request, and it would 
create an invalid filter if the component was provided as an empty string. It 
will now treat components provided as empty strings as if they had been 
null.</p>
   </li>
   <li>
   <p>We updated the logic that the LDAP SDK uses to pare entries down to a 
specified set of attributes (including in the in-memory directory server and 
the <code>ldifsearch</code> command-line tool) to improve its behavior if it 
encounters an entry with a malformed attribute description (for example, one 
that contains characters that aren’t allowed). Previously, this would result in 
an internal error, but it will now make a best-attempt effort to handle the 
invalid name.</p>
   </li>
   <li>
   <p>We updated the <code>TimestampArgument</code> class to allow it to accept 
timestamps in the ISO 8601 format described in RFC 3339 (e.g., 
2023-11-30T01:02:03.456Z). Previously, it only accepted timestamps in the 
generalized time format (or a generalized time representation that didn’t 
include any time zone information, which was treated as the system’s local time 
zone).</p>
   </li>
   <li>
   <p>We updated the <code>JSONBuffer</code> class to add an 
<code>appendField</code> method that can be used to append a generic field 
without knowing the value type. Previously, it only allowed you to append 
fields if you knew the type of the value.</p>
   </li>
   <li>
   <p>We added new <code>BinarySizeUnit</code> and <code>DecimalSizeUnit</code> 
enums that can be used when dealing with a quantity of data, like the size of a 
file or the amount of information transferred over a network. Each of the enums 
supports a variety of units (bytes, kilobytes, megabytes, gigabytes, terabytes, 
petabytes, exabytes, zettabytes, and yottabytes), but the 
<code>BinarySizeUnit</code> variant assumes that each subsequent unit is 1024 
times greater than the previous (e.g., one kilobyte is treated as 1024 bytes), 
while <code>DecimalSizeUnit</code> assumes that each subsequent unit is 1000 
times greater than the previous (e.g., one kilobyte is treated as 1000 
bytes).</p>
   </li>
   <li>
   <p>We updated the client-side support for invoking the LDIF export 
administrative task in the Ping Identity Directory Server to include support 
for activating one or more post-LDIF-export task processors, which can be used 
to perform additional processing after the data is successfully exported.</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>          &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><a 
href="https://github.com/pingidentity/ldapsdk/commit/8b21d0a4c6eb8b5c3e60a96fc3e9e13b9c2f650f";><code>8b21d0a</code></a>
 Improve ldapsearch/ldapmodify --proxyAs handling</li>
   <li><a 
href="https://github.com/pingidentity/ldapsdk/commit/eb22dc83322d59b460b6510a216a2ab935591e1c";><code>eb22dc8</code></a>
 Add a release note about dropping Java 7 support</li>
   <li><a 
href="https://github.com/pingidentity/ldapsdk/commit/75aea3f7838459be0a460fbf0b3c5a7973bfc5fa";><code>75aea3f</code></a>
 Avoid a NullPointerException in SearchEntryParer</li>
   <li><a 
href="https://github.com/pingidentity/ldapsdk/commit/f485f6a5ef6ad1c74cec2229844276efe77e27f5";><code>f485f6a</code></a>
 Add size unit enums</li>
   <li><a 
href="https://github.com/pingidentity/ldapsdk/commit/3dad7ef3276b5667c4fc0a5438448aabc6dccd26";><code>3dad7ef</code></a>
 Add JSONBuffer.appendField</li>
   <li><a 
href="https://github.com/pingidentity/ldapsdk/commit/c93253dae5e9f243dc0cb1ee27a1b83c63e41e61";><code>c93253d</code></a>
 TimestampArgument support for RFC 3339</li>
   <li><a 
href="https://github.com/pingidentity/ldapsdk/commit/42a4d404bf945f78ce210510a5097e272560f5c1";><code>42a4d40</code></a>
 Add support for post-LDIF-export task processors</li>
   <li><a 
href="https://github.com/pingidentity/ldapsdk/commit/a2d25c20a0b3ca9e05b8caef2b318d5da071de7d";><code>a2d25c2</code></a>
 Better handle empty comps in substring filters</li>
   <li><a 
href="https://github.com/pingidentity/ldapsdk/commit/3dd7837c631e79b08bd2bfd212c123342a5907ac";><code>3dd7837</code></a>
 Post-6.0.10 updates</li>
   <li>See full diff in <a 
href="https://github.com/pingidentity/ldapsdk/compare/6.0.10...6.0.11";>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: [email protected]

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

Reply via email to