Bump unboundid-ldapsdk from 6.0.3 to 6.0.4

[dependabot]

Bumps unboundid-ldapsdk from 6.0.3 to 6.0.4.

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.4&lt;/h3&gt;
  &amp;lt;p&amp;gt;
    The following changes were made between the 6.0.3 and 6.0.4 releases:
  &amp;lt;/p&amp;gt;

  &amp;lt;ul&amp;gt;
    &amp;lt;li&amp;gt;
      Fixed an issue in the Filter.matchesEntry method that could cause it to throw an
      exception rather than an appropriate Boolean response when evaluating an AND or
      an OR filter in which one of the nested components is not valid (for example, if
      the assertion value does not conform to the syntax for the associated attribute
      type).  This could cause problems for other LDAP SDK components that may rely on
      filter matching, like the in-memory directory server or the ldifsearch
      command-line tool.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
    &amp;lt;/li&amp;gt;

    &amp;lt;li&amp;gt;
      Addressed a potential conflict in the way that decodeable controls are
      registered with the LDAP SDK that may have caused issues when trying to
      instantiate a control.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
    &amp;lt;/li&amp;gt;

    &amp;lt;li&amp;gt;
      Fixed an issue in the JVM-default trust manager implementation in which it did
      not properly look for a trust store file named &amp;quot;jssecacerts&amp;quot; in accordance with
      the JSSE specification.  It had previously only looked for a file named
      &amp;quot;cacerts&amp;quot;.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
    &amp;lt;/li&amp;gt;

    &amp;lt;li&amp;gt;
      Updated the logic used to select the default set of supported cipher suites to
      no longer exclude suites starting with &amp;quot;SSL_&amp;quot; by default on JVMs with a vendor
      string that includes &amp;quot;IBM&amp;quot;.  IBM JVMs appear to use the &amp;quot;SSL_&amp;quot; prefix for some
      or all cipher suites, including those that are not associated with a legacy SSL
      protocol.  Also, added a TLSCipherSuiteSelector.setAllowSSLPrefixedSuites
      method that can be used to override the default behavior as needed.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
    &amp;lt;/li&amp;gt;

... (truncated)

Commits

• See full diff in compare view

You can trigger a rebase of this PR 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)