dependabot[bot] opened a new pull request, #2465: URL: https://github.com/apache/cxf/pull/2465
Bumps [com.unboundid:unboundid-ldapsdk](https://github.com/pingidentity/ldapsdk) from 7.0.2 to 7.0.3. <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.3&lt;/h3&gt; &lt;p&gt; The following changes were made between the 7.0.2 and 7.0.3 releases: &lt;/p&gt; &lt;ul&gt; &lt;li&gt; Fixed an issue in which the LDAP SDK did not properly handle certificates with a notBefore or notAfter timestamp that fell in the year 2049 if that timestamp was encoded with the antiquated UTCTime syntax, which only uses two digits to express the year. The X.509 specification indicates that UTCTimestamp values with years of &quot;00&quot; through &quot;49&quot; should be interpreted as the years 2000 through 2049, and that UTCTime years of &quot;50&quot; through &quot;99&quot; should be interpreted as the years 1950 through 1999, but the LDAP SDK incorrectly treated a year of &quot;49&quot; as 1949 instead of 2049. All other year values were properly handled in accordance with the X.509 specification. &lt;br&gt;&lt;br&gt; &lt;/li&gt; &lt;li&gt; Updated client-side support for the Ping Identity-proprietary transaction settings request control to add the ability to request that the server acquire a scoped lock under certain conditions. Scoped locks may be useful when it is possible to identify operations that are more likely than others to result in lock conflicts (for example, in a multi-tenant deployment, operations targeting entries in the same tenant are probably more likely to conflict than operations targeting entries in different tenants), to limit the potential performance impact in the event of a conflict. We also added the ability to override the conditions under which the server may attempt to acquire a single-writer lock within the associated backend, which could previously only be controlled through the server configuration, and to indicate whether the control should be taken into consideration when the operation is replicated to other servers in the topology. &lt;br&gt;&lt;br&gt; &lt;/li&gt; &lt;li&gt; Updated the ldifmodify tool to report an error if any of the sourceLDIF, changesLDIF, or targetLDIF arguments referred to the same file. They must all refer to different files. &lt;br&gt;&lt;br&gt; </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 /> [](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: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
