Bump unboundid-ldapsdk from 6.0.8 to 6.0.9 in /full

[dependabot[bot]]

Bumps unboundid-ldapsdk from 6.0.8 to 6.0.9.

Release notes

Sourced from unboundid-ldapsdk's releases.

UnboundID LDAP SDK for Java 6.0.9

We have just released version 6.0.9 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.

As announced in the previous release, the LDAP SDK source code is now maintained only at GitHub. The SourceForge repository is still available for its discussion forum, mailing lists, and release downloads, but the source code is no longer available there.

You can find the release notes for the 6.0.9 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 made it possible to customize the set of result codes that the LDAP SDK uses to determine whether a connection may no longer be usable. Previously, we used a hard-coded set of result codes, and that is still the default, but you can now override that using the ResultCode.setConnectionNotUsableResultCodes method.

• We added a new HTTPProxySocketFactory class that can be used to establish LDAP and LDAPS connections through an HTTP proxy server.

• We added a new SOCKSProxySocketFactory class that can be used to establish LDAP and LDAPS connections through a SOCKSv4 or SOCKSv5 proxy server.

• We updated the ldap-diff tool to add a --byteForByte argument that can be used to indicate that it should use a byte-for-byte comparison when determining whether two attribute values are equivalent rather than using a schema-aware comparison (which may ignore insignificant differences in some cases, like differences in capitalization or extra spaces). Previously, the tool always used byte-for-byte matching, but we decided to make it a configurable option, and we determined that it is better to use schema-aware comparison by default.

• We fixed an issue in which a non-default channel binding type was not preserved when duplicating a GSSAPI bind request. We also added a GSSAPIBindRequest.getChannelBindingType method to retrieve the selected channel binding type for a GSSAPI bind request.

• We added a ResultCode.getStandardName method that can be used to retrieve the name for the result code in a form that is used to reference it in standards documents. Note that this may not be available for result codes that are not defined in known specifications.

• We added a mechanism for caching the derived secret keys used for passphrase-encrypted input and output streams so that it is no longer necessary to re-derive the same key each time it is used. This can dramatically improve performance when the same key is used multiple times.

• We updated the StaticUtils.isLikelyDisplayableCharacter method to consider additional character types to be displayable, including modifier symbols, non-spacing marks, enclosing marks, and combining spacing marks.

• We added a new StaticUtils.getCodePoints method that can be used to retrieve an array of the code points that comprise a given string.

• We added a new StaticUtils.unicodeStringsAreEquivalent method that can be used to determine whether two strings represent an equivalent string of Unicode characters, even if they use different forms of Unicode normalization.

• We added a new StaticUtils.utf8StringsAreEquivalent method that can be used to determine whether two byte arrays represent an equivalent UTF-8 string of Unicode characters, even if they use different forms of Unicode normalization.

• We added a new StaticUtils.isValidUTF8WithNonASCIICharacters method that can be used to determine whether a given byte array represents a valid UTF-8 string that contains at least one non-ASCII character.

• We updated the client-side support for the collect-support-data administrative task to make it possible to specify the start and end times for the set of log messages to include in the support data archive.

• We updated the documentation so that the latest versions of draft-melnikov-sasl2 and draft-melnikov-scram-sha-512 are included in the set of LDAP-related specifications.

Changelog

Sourced from 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 6.0.9&lt;/h3&gt;

      &lt;p&gt;
        The following changes were made between the 6.0.8 and 6.0.9 releases:
      &lt;/p&gt;

      &lt;ul&gt;
        &lt;li&gt;
          The LDAP SDK source code will now only be updated on GitHub and will no longer
          be maintained on SourceForge.  The SourceForge repository will still be
          available for historical releases, but the trunk has been replaced with a README
          file indicating that updated code is now only on GitHub.  It required effort to
          keep both repositories in sync, and GitHub is removing its support for acting as
          a Subversion repository, which that synchronization process relied upon.  The
          SourceForge project will still be updated with downloads for new releases, and
          the discussion forums and mailing lists will remain available.
          &lt;br&gt;&lt;br&gt;
        &lt;/li&gt;

        &lt;li&gt;
          Added an option for customizing the set of result codes that the LDAP SDK may
          use to determine whether a connection may no longer be usable.  Previously, it
          used a hard-coded set of result codes for this purpose, and that set is still
          the default, but it is now possible to override that with a provided set of
          result codes.
          &lt;br&gt;&lt;br&gt;
        &lt;/li&gt;

        &lt;li&gt;
          Added a new HTTPProxySocketFactory class that can be used to allow establishing
          LDAP and LDAPS connections through an HTTP proxy server, and added a new
          SOCKSProxySocketFactory class that can be used to allow establishing connections
          through a SOCKSv4 or SOCKSv5 proxy server.  Communication with the proxy server
          itself must be unencrypted (although communication with the target LDAP server
          may optionally be end-to-end encrypted with TLS), and the proxy server must not
          require authentication.
          &lt;br&gt;&lt;br&gt;
        &lt;/li&gt;

        &lt;li&gt;
          Updated the ldif-diff tool to add a --byteForByte argument that can be used to
          indicate that it should not ignore differences between source and target entries

... (truncated)

Commits

• 42839dd Update the OID registry
• c282150 Include channel binding type in GSSAPI duplicate
• 1c5e7aa Fix a typo in ldap-diff
• effd5ea Use a better filter for IMDS.getEntry
• 55b7740 Add ResultCode.getStandardName
• 1ad2acd Fix a typo in oid-registry.json
• e1f9c59 Add support for HTTP proxy servers
• bad56ad Add support for using SOCKS proxies
• 46f087e Update the OID registry
• cdc33af Update release notes with SourceForge repo update
• 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 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)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.