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.3.2 (2026-10-13)

Delegated writes recover after directory disconnects, and operation logs now record write durations and outcomes. The bundled compression library also receives a security fix. No configuration or database changes are required.

Security

  • Compression library security update. Updated the compression library bundled with 3.3.1 to address CVE-2026-106451. Existing data remains readable; no configuration changes are required.

Added

  • LDAP writes show their timing. Add, Modify, Delete and rename requests that IdentityScribe forwards to the directory now appear in the operation log as LDAP.Add, LDAP.Modify and LDAP.Delete with their duration and result, and in scribe_channel_request_duration_seconds with op="add", op="modify" or op="delete"; a rename counts as a modify. Each write shows how long the directory took to answer as an LDAP.Delegation event, so a slow write tells whether the time went to IdentityScribe or to the directory, and whether the write first had to connect to the directory. As with searches, slow and failed writes now appear in the operation log by default, except fast ones refused because the entry is missing or the request is invalid; to log every write, see Time LDAP writes. Requests and their results are unchanged.

Fixed

  • Delegated writes recover after disconnects. Creates and modifications in 3.3.0 and 3.3.1 could keep failing with UNAVAILABLE after a directory connection dropped; Scribe now restores the connection for subsequent requests without repeating an uncertain write, and no configuration change is needed.
  • Invalid continuations give clear guidance. Rejected paging or VLV continuations in 3.3.0 and 3.3.1 now say Paging or VLV continuation is not valid on this connection; restart the search. instead of claiming that the authorization identity changed.
  • Malformed paging returns protocol errors. Malformed paged-results request controls in 3.3.0 and 3.3.1 now receive PROTOCOL_ERROR (2) and The paged results request control is malformed. instead of a misleading continuation rejection.