Bump com.unboundid:unboundid-ldapsdk from 7.0.2 to 7.0.3

[dependabot]

Bumps com.unboundid:unboundid-ldapsdk from 7.0.2 to 7.0.3.

Changelog

Sourced from com.unboundid:unboundid-ldapsdk's changelog.

          <div align="right">

$TARGET="offline"LDAPSDKHomePage${TARGET="offline"} Product Information

          <h2>Release Notes</h2>
      &lt;h3&gt;Version 7.0.3&lt;/h3&gt;
  &amp;lt;p&amp;gt;
    The following changes were made between the 7.0.2 and 7.0.3 releases:
  &amp;lt;/p&amp;gt;

  &amp;lt;ul&amp;gt;
    &amp;lt;li&amp;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 &amp;quot;00&amp;quot; through &amp;quot;49&amp;quot; should be interpreted as the years 2000 through 2049, and
      that UTCTime years of &amp;quot;50&amp;quot; through &amp;quot;99&amp;quot; should be interpreted as the years 1950
      through 1999, but the LDAP SDK incorrectly treated a year of &amp;quot;49&amp;quot; as 1949 instead
      of 2049.  All other year values were properly handled in accordance with the
      X.509 specification.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
    &amp;lt;/li&amp;gt;

    &amp;lt;li&amp;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.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
    &amp;lt;/li&amp;gt;

    &amp;lt;li&amp;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.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;

... (truncated)

Commits

• See full diff in compare view

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 commands and options

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)