Skip to content

Version History

  • Changes

    Read the outcomes and fixes in this release.

  • Upgrade

    Check migration guidance before changing an existing deployment.

Check release changes before choosing an upgrade.

Find the relevant version below and check breaking changes before scheduling an upgrade.

Next: Upgrade guidance

Version v3.2.1 (2026-09-21)

Security

  • Compression libraries receive security updates. Updated both compression libraries to address known vulnerabilities. No configuration changes are required.

Fixed

  • Searches no longer stall until restart — On a busy service, directory searches on every channel could stop returning results until the service was restarted, while synchronization and health checks still reported a healthy instance. This permanent stall can no longer occur. All 3.x releases up to and including 3.2.0 are affected, so rolling back to an earlier 3.x release does not avoid the problem.
  • Searches recover after clients give up or time out — Searches on every channel could stop after clients repeatedly gave up on slow requests or searches ran into their time limit while waiting, leaving a restart as the only recovery. Abandoned requests no longer cause this permanent stall. This affects releases from 3.0.0-rc.3 through 3.2.0, including stable releases 3.0.0, 3.1.0, and 3.2.0.
  • Browser login works for local and LDAP accounts together — With auth.methods = [local, ldap], the login form now accepts both configured local accounts and LDAP users. In 3.2.0, adding a local technical account made browser login local-only and LDAP users were rejected with “Invalid credentials”. No configuration change is needed; if you set auth.session.method = ldap as a workaround, you can keep it to keep technical accounts out of the browser, or remove it to allow both. Wherever local is accepted, a local account signs in only with its configured password, and a wrong password for a local DN or alias is never tried against LDAP. Surrounding whitespace in a login name, including non-breaking and invisible spaces from copy and paste, is now ignored for local accounts on all channels (browser login, HTTP Basic, and LDAP bind), and a local account alias configured with surrounding whitespace matches its trimmed form. [local] and [ldap] on their own, OIDC, ROPC, HTTP Basic, and LDAP bind behave as before.
  • MCP tools name wrongly typed arguments — A Data MCP tool call whose arguments use the wrong JSON types, such as a string limit or an array entryType, now returns an invalid-argument error that names the argument. Earlier releases reported this as a temporary failure.
  • Observe MCP rejects unknown scopes — An observe call whose scope is not one of the documented values now returns an invalid-argument error. The submitted value is truncated and is not copied into the public error text, so a very long scope cannot inflate the response. Earlier releases silently returned the summary.
  • MCP ref lookups now resolve — Asking ref for an error code, metric, configuration key, or attribute now returns the matching documentation URL. Earlier releases returned no match. When nothing matches, the suggested queries are names that do resolve.