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

[dependabot]

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

Release notes

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

UnboundID LDAP SDK for Java 7.0.3

We have just released version 7.0.3 of the UnboundID LDAP SDK for Java. It is available for download from GitHub and SourceForge, and it is available in the Maven Central Repository. You can find the release notes for this release (and all previous versions) at https://docs.ldap.com/ldap-sdk/docs/release-notes.html, but here’s a summary of the changes:

• We 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 encode the year). It incorrectly used a year of 1949 instead of 2049.

• We updated the ldifmodify tool so that it will report an error if any of the sourceLDIF, changesLDIF, or targetLDIF arguments refer to the same file. Previously, the tool would run, but could yield incomplete results if an input file was also used as an output file.

• We updated the IP address argument value validator to improve performance and to catch additional types of malformed IPv4 addresses that were previously accepted due to leniency in Java’s InetAddress.getByName implementation.

• We simplified and improved the toLowerCase, toUpperCase, and getBytes methods in the StaticUtils class. The former implementations were more efficient than the versions provided in the Java String class in older Java versions when primarily dealing with ASCII strings, but this is no longer the case in newer versions of Java where strings are backed by byte arrays rather than character arrays.

• We updated client-side support for the Ping-proprietary transaction settings request control to make it possible to request that the server acquire a lock using a client-specified scope under a specified set of conditions. This allows more control in the event of lock conflicts in cases where the client is able to determine which operations are most likely to conflict with each other. For example, in a multi-tenant server, it may be useful to specify a scope that includes a tenant-specific identifier so that only operations associated with that tenant will be affected by the scoped lock.

• We also updated the transaction settings request control to make it possible to override the conditions under which the server may attempt to acquire a single-writer lock. This was previously only controlled through the server configuration.

• We improved error reporting in the dump-dns tool for use with the Ping Identity Directory Server.

• We updated client-side support for the Ping Identity Directory Server’s version monitor entry to handle attributes used to indicate whether the server is running in FIPS 140-2-compliant or FIPS 140-3-compliant mode.

• We updated the documentation to include the newest versions of the draft-bucksch-sasl-passkey, draft-bucksch-sasl-rememberme, draft-codere-ldapsyntax, draft-ietf-kitten-sasl-ht, draft-ietf-kitten-sasl-rememberme, and draft-schmaus-kitten-sasl-ht specifications.

UnboundID LDAP SDK for Java 7.0.2

We have just released version 7.0.2 of the UnboundID LDAP SDK for Java. It is available for download from GitHub and SourceForge, and it is available in the Maven Central Repository. You can find the release notes for this release (and all previous versions) at https://docs.ldap.com/ldap-sdk/docs/release-notes.html, but here’s a summary of the changes:

• We added support for using the 2.x version of the Bouncy Castle FIPS-compliant security provider, which provides support for FIPS 140-3 compliance. The 1.x version of the library, offering FIPS 140-2 compliance, is still supported. To use the LDAP SDK in this mode, you should ensure that the necessary jar files are in the classpath, and then you should call CryptoHelper.setUseFIPSMode("BCFIPS2") as early as possible in the life of the application.

• We added a new PropertyManager class that can be used to retrieve the value of specified properties using either system properties or environment variables. Values can be optionally parsed as Booleans, numbers, or comma-delimited lists. Most uses of system properties within the LDAP SDK have been updated to support the new PropertyManager mechanism so that it’s possible to set values as environment variables as an alternative to system properties.

• We fixed a bug in the SSLUtil.certificateToString method that prevented it from including the notBefore and notAfter timestamps in the string representation.

• We added client-side support for the Ping Identity Directory Server’s new to-be-deleted accessibility state for use with the get subtree accessibility and set subtree accessibility extended operations.

• We updated the MoveSubtree utility class to provide the ability to use the new to-be-deleted accessibility state (as an alternative to the hidden state) for the target subtree before starting to remove entries from the source server.

• We added a new SubtreeAccessibilityState.isMoreRestrictiveThan method that can be used to determine whether one accessibility state is considered more restrictive than another.

• Updated the documentation to include the latest versions of the following LDAP-related specifications:

  • draft-coretta-ldap-subnf-01
  • draft-coretta-oiddir-radit
  • draft-coretta-oiddir-radsa
  • draft-coretta-oiddir-radua
  • draft-coretta-oiddir-roadmap
  • draft-coretta-oiddir-schema
  • draft-ietf-kitten-scram-2fa
  • draft-melnikov-sasl2
  • draft-melnikov-scram-bis
  • draft-melnikov-scram-sha-512
  • draft-melnikov-scram-sha3-512

UnboundID LDAP SDK for Java 7.0.1

... (truncated)

Changelog

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

          <div align="right">

${TARGET="offline"} LDAP SDK Home Page ${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

• b2dd76d IPAddressArgumentValueValidator improvements
• d9549c6 Update several LDAP-related drafts
• 6443010 Add FIPS support to the version monitor entry
• 155b4ae Reject conflicting ldifmodify arguments
• d18e282 Add replication support to txn settings control
• bf81663 Update toLowerCase, toUpperCase, and getBytes
• 865a478 Fix the OID reference file encoding
• 9d86fa5 Further updates to the txn settings control
• 843b32a Improve dump-dns error reporting
• 11a99b5 Update txn settings control for scoped locks
• Additional commits viewable 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)