Skip to content

All versions since v3.3.2 (2026-10-13)

  • 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

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.

v3.3.3 (2026-10-18)

Bearer tokens and token claims no longer reach logs or traces, access rules match their values literally, and a stopped LDAP listener now restarts on its own; upgrades with renamed entries finish, very large groups load again while oversized entries are refused when written, and two quick changes to an entry keep the newer value. Four changes need action, listed under Breaking: heap dumps need a directory only the service account can read, Observe actions sent from other websites are refused, HTTPS sessions need the protected session cookie, and identity providers must report their configured issuer; bearer sign-in also uses the auth.http trust store now. Logs written by earlier releases may contain tokens and personal data, so delete or restrict them.

Breaking

  • Heap dumps need a private directory. BREAKING: POST /observe/memory/heap-dump now refuses with 503 unless monitoring.memory.heap-dump.directory is owned by the service account and grants no access to anyone else, because a dump holds credentials and personal data; point the setting at such a directory or let Scribe create it. Filesystems without POSIX permissions or ACLs are refused as well.
  • Other websites cannot trigger Observe actions. BREAKING: Inbox actions, the plan-mode kill switch and heap dumps now answer 403 and change nothing when a browser session sends them from another website, including another host of the same domain, or without origin information, so a page elsewhere can no longer act with a signed-in operator’s rights; Inbox actions and the kill switch also answer 415 unless the body is sent with Content-Type: application/json. The Observe pages keep working. All 3.x releases up to and including 3.3.2 are affected; see Sign-in form protection. Migration: switch scripts that call these actions with a session cookie to a bearer token or HTTP Basic credentials, which are not affected, and send JSON bodies with Content-Type: application/json.
  • HTTPS sessions need the protected session cookie. BREAKING: Over HTTPS, Scribe now reads only the session cookie it sets over HTTPS, which no other host and no plain-HTTP page can set; a session cookie left over from a plain-HTTP sign-in, or one hidden inside another cookie’s value, is ignored. Behind a reverse proxy that terminates TLS, a request counts as HTTPS when the proxy is listed in http.requested-uri-discovery and reports https; Scribe then sets the protected cookie with Secure, and access rules on request.secure match. Migration: sign in again after moving a deployment from HTTP to HTTPS; behind a TLS-terminating proxy, enable http.requested-uri-discovery with the proxy as a trusted proxy so sessions get the protected cookie.
  • Identity providers must report their configured issuer — BREAKING: Scribe now rejects a provider whose discovery document names an issuer other than its issuer or public-issuer — bearer tokens, password sign-in and token introspection through that provider fail. Migration: set public-issuer to the issuer your identity provider reports. See Authentication.

Security

  • Access rules match values literally. Underscores, percent signs and backslashes in a starts-with, ends-with, contains or wildcard value acted as wildcards, so a rule could match request paths, hosts or accounts it did not name; they now match only themselves, and only * in a wildcard value matches any text, as documented. All 3.x releases up to and including 3.3.2 are affected; see Access rules.
  • Bearer tokens kept out of logs. A rejected LDAP bearer bind could write the client’s complete bearer token into the operation log, where anyone with log access could reuse it; the log now records only the reason. Delete or restrict logs from earlier releases, and treat tokens that were still valid at the time as exposed.
  • Token claims kept out of logs. A token rejected by a claim check, such as issuer, expiry or audience, wrote its decoded claims, including subject and e-mail address, into the operation log, and introspection failures logged audience values; the log now names the failed checks and claims, the token’s issuer and the expected value, and no claim values. With SCRIBE_LOG_JOSE4J = debug, token headers no longer reach the library log. Delete or restrict logs from earlier releases according to your personal-data retention rules.
  • Rejected opaque tokens kept out of traces. With a UserInfo endpoint configured, an opaque token containing characters not allowed in an HTTP header was written in full into the trace and the operation log; both now record only the reason.
  • Bearer sign-in honours identity provider settings. Bearer tokens are now checked with signing keys and provider details fetched through the auth.http trust store and timeouts, so identity providers with a private certificate authority work without changing the system trust store. While the identity provider is unreachable, Scribe retries it at most every few seconds, backing off to once a minute, instead of on every request, and keeps using the last signing keys it fetched. A provider’s Cache-Control: max-age now counts as at least one minute and at most one day, and provider answers larger than 512 KiB are refused. A failed token request now logs only the provider’s status, the kind of answer (such as JSON or HTML) and its size, no longer the start of its answer or its full content type, which could echo a password or authorization code.

Changed

  • Token rejections report their actual reason. Rejection codes no longer depend on words inside the token: expired tokens report AUTH_TOKEN_EXPIRED, tokens for another audience AUTH_TOKEN_INVALID_AUDIENCE, and a token with an unknown signing algorithm AUTH_TOKEN_INVALID_SIGNATURE with LDAP result 49 and HTTP 401 instead of AUTH_JWKS_ERROR with 52 and 503. All other rejections keep their LDAP result and HTTP status.

Fixed

  • Upgrades with renamed entries finish. An upgrade that rebuilds stored entries failed on every start when an entry had been renamed, including entries deleted later; renamed entries now come back with their new name and last change time.
  • Groups with very many members are stored and read again. An entry with more than 65,536 values in one attribute, such as a large group’s members, was stored but then failed to load, so later changes to it, directory reads of it and restores failed; such entries, including those stored by earlier releases, now load normally. An entry beyond the supported size (more than 4,096 attributes, more than about four million values, an attribute name over 1,024 bytes, a value over 16 MiB or 64 MiB of values in total) is now refused when it is written, with an error naming the exceeded limit, and the previously stored version and its history stay unchanged.
  • /observe/health/ready fails while searches are stalled. Like /readyz, it and the combined /observe/health now return 503 with a query-stall check while every query permit stays in use, unless monitoring.readiness.fail-on-query-stall is false; see Kubernetes probes.
  • Stopped LDAP listeners restart. When an error such as running out of threads stopped an LDAP or IdentityHub listener, it stayed down until Scribe was restarted while the channel reported healthy; it now restarts as set by retry.services, and the channel reports unhealthy until it accepts connections again. On Linux with use-reuse-address = false, the restart retries while an old connection still holds the port and logs ldap_listener_rebind_failed for each attempt.
  • Shutdown no longer waits for stalled clients. Stopping Scribe or a listener no longer waits for a client that has stopped reading its responses.
  • Reconciliation counts only recorded entries. When the database could not record that a page of entries was verified, reconciliation still counted the page and searched the same entries again; it now retries briefly and otherwise stops the run without counting that page.
  • A slow directory no longer ties up database connections. When a change notification arrived without the entry’s object classes, Scribe re-read the entry from the directory while holding a database connection and the entry’s row lock; it now holds them only for the write.
  • Two quick changes keep the newer value. When the directory changed the same entry twice in quick succession, Scribe could store the older values last and add a change back to them to the entry’s history, although the directory still held the newer values; the newer values now stay stored and the history shows no such change. Entries already affected are corrected by their next change or a resync.
  • Later queries keep their settings. A session setting that failed to apply or restore could change plan choice or timeouts for unrelated later queries on the same pooled connection.
  • Transient errors retry under every system locale. Database, LDAP and HTTP operations now also retry temporary I/O failures under Turkish or Azerbaijani system locales.
  • A missing license file is named. When license.file points at a file that does not exist or cannot be read, verification now fails with License file not found or not readable: <path> and where the setting came from.
  • The production template starts. config/production.conf failed startup validation; it now serves the Operator UI and REST admin on the internal socket together with Observe, and all templates note that production needs SCRIBE_AUTH_SESSION_KEYS. See Network isolation.
  • Missing session keys stop startup at once. With auth.enabled = false and browser sessions on, the default when any UI is enabled, a production start without auth.session.cookie-keys now fails validation with AUTH_SESSION_KEYS_REQUIRED instead of retrying until retry.services.max-attempts runs out.
  • The Helm stack serves monitoring on port 9001. The chart exposed port 9001, but Scribe never opened it; the chart now configures health and /observe on 9001, matching the Docker bundle, and its probes check that port.
  • The Helm stack’s Grafana reaches Prometheus and Tempo. The stack now serves Prometheus on 9090 and points the Tempo datasource at its HTTP port, so dashboards and trace lookups work after install.
  • Health endpoints answer HEAD. /livez, /readyz, /startedz and /healthz answered HEAD with 404, so probes such as wget --spider saw a running instance as failed; they now return the same status as GET, without a body.
  • Delegated searches keep the client’s attribute spelling. Since 3.0, searches forwarded to the directory, such as those under ldap.ignore-contexts, sent unmapped attribute names in lowercase, so a client asking for workforceID could receive workforceid and find no values; Scribe now forwards them as the client spells them.
  • Sorted searches by position return each entry once. A sorted search that starts at a numbered position, such as an LDAP virtual list view request by offset, could repeat and skip entries when some had no value for the sort attribute; each position now matches the complete sorted result. All 3.x releases up to and including 3.3.2 are affected.
  • Paged sorted searches return long values once. With the default database.query.sort.long-value-tiebreaker = deterministic, paging through values that share their first 256 characters could repeat some entries and skip others; each page now continues exactly where the previous one ended.
  • Case-only changes replace the old spelling. When the directory changed only the letter case of one value of a multi-valued attribute, Scribe kept both spellings in searchable data and recorded only an addition; it now keeps the new spelling and records the old one as removed. Values recorded before this release are not corrected.
  • Per-transcribe task limit takes effect. The documented max-task-concurrency setting of a transcribe was ignored in favour of the database pool size; it now applies, capped at concurrency. See Transcribes.
  • Browser sign-in works behind a proxied identity provider. When public-issuer differed from issuer, as is usual behind a reverse proxy, every browser sign-in was rejected; it now succeeds, and sign-ins from other identity providers are still refused.
  • Failed MCP tool calls count as failures. A tool call that returned an error, such as an invalid argument, was recorded as ok in the per-tool metrics and the audit log; it is now recorded as unknown, so error rates show.
  • Scheduled maintenance stops at shutdown. Scheduled and interval maintenance runs now stop at their next safe point when Scribe shuts down, as manual runs already did, instead of delaying shutdown until the sweep ends.
  • Entry views show the current state. In the Operator UI, returning to an entry or to a relative time such as “1 hour ago” showed the state from your first visit, and a deleted entry reappeared; the view now checks for the latest state and says when that check failed, with a “Try again” button.
  • Entry history shows the time you chose. In the Operator UI, choosing a time before the entry existed or older than the loaded history jumped to a later change; the view now shows the entry at that time, or says it did not exist then.
  • Entry comparisons show loading and errors. In the Operator UI, comparing two states of an entry showed every value as added or removed while one side was loading or had failed; it now shows that it is loading, or an error with a “Try again” button.
  • The Browse Hub says when its data is missing. When monitoring data failed to load or refresh, Browse Hub cards showed zeros, “None”, “All clear” or old values as if current, also after a reload; they now show “Loading” or “Unavailable”, with a “Try again” button when nothing loaded or a refresh failed.
  • Observe views work with hints off. With monitoring.hints.enabled = false, the Doctor, Services, Build Queue, Ingest, JVM, LDAP Forwarding and Pipeline views showed only an error; they now show their data and mark values that did not refresh as unavailable.
  • The Changes feed shows the right hourly rate. In the Operator UI, the Changes summary rate read 3,600 times too low; 3,600 changes in one hour now show as 3.6k/h.

v3.3.4 (2026-10-22)

This release fixes one startup failure in 3.3.3 and updates build and documentation tooling for known advisories. If you skipped a startup step to work around it, read the action under Fixed before you start 3.3.4.

Fixed

  • Startup no longer stops while cleaning up entry histories. When startup had to clean up entry histories that earlier resyncs had duplicated, Scribe could stop with Unable to discover event-stream normalization candidates, caused by Cannot change transaction read-only property in the middle of a transaction. We reproduced this failure: a new database connection reached Scribe with a transaction still open. New connections now start without one, which fixes the reproduced failure. Installations whose next start runs this cleanup, mostly the first start after an upgrade, may be affected. Action: if you skipped the cleanup by setting eventStreamNormalizationVersion in the subscriptions table, remove that marker right before the first start of 3.3.4, so the cleanup runs on that start:

    BEGIN;
    UPDATE subscriptions
    SET state = state - 'eventStreamNormalizationVersion'
    WHERE id LIKE 'identity-scribe:state:%';
    SELECT id, state ? 'eventStreamNormalizationVersion' AS marker_present
    FROM subscriptions WHERE id LIKE 'identity-scribe:state:%';
    COMMIT;

    Every row should show marker_present = false. After that start, the log reports the cleanup for each entry type and the marker is set again. Without the marker workaround, no action is needed.

v3.3.5 (2026-10-26) Latest

Access and log rule conditions now match as written: conditions with dotted values, such as e-mail addresses or IP prefixes, and conditions in outer parentheses joined with and or or could match other requests than written, so deny rules could miss and allow rules could admit identities they were meant to exclude. Two changes may need action, both under Breaking: a parenthesised rule condition that reads both as one comparison and as several now stops startup with an error naming the rule, and REST, GraphQL and MCP search filters such as (cn=x or sn=y) are now read as two comparisons. Bearer sign-in keeps working while the identity provider’s key endpoint is unavailable, forwarded LDAP sign-ins keep their own directory account after a lost directory connection, and wrong-issuer errors stay readable. Set database passwords through database.password or POSTGRES_PASSWORD rather than inside a connection address, where they can reach debug logs; build and documentation tooling is also updated for known advisories.

Breaking

  • Rule conditions in outer parentheses match as written. BREAKING: An access or log rule condition wrapped in outer parentheses and joined with and or or, such as a deny rule (subject.principal.id=alice@example.com or subject.principal.id=bob@example.com), was read as a single comparison with the rest of the condition as its value. With = such a condition never matched, so deny rules did not apply and allow rules admitted no one; with >=, <= or ~= it could match far more than written, so an allow rule such as (subject.principal.id>=alice and subject.principal.id<b) admitted identities like carol.white@example.com that it was meant to exclude. These conditions now work as written. Search filters sent over REST, GraphQL or MCP follow the same rule, so (cn=x or sn=y) now searches for either comparison; to search for a value that contains or followed by =, write the = as \3d. Filters sent by LDAP clients are unchanged. A rule condition that reads both as one comparison and as several comparisons joined by and, or, &&, || or a space, such as (subject.principal.id=alice or subject.principal.id eq bob) or (subject.principal.id>=a&&subject.principal.id<b), now stops startup with an error naming the rule. Migration: remove the outer parentheses, or, for a value that really contains such text, escape the characters that separate it, such as each space as \20. Values that cannot be read as several comparisons, such as (subject.principal.id=uid=alice,ou=Research and Development,dc=example,dc=com), keep matching as written.

Security

  • Rule conditions preserve dotted values. Since 3.0.0, access and log rules with dotted or underscored values, such as e-mail addresses, IP prefixes and operation names, could compare against a rewritten value when using a word operator (eq, startswith, contains, etc.) or spaces around the operator. Such conditions could match too few or too many requests: deny rules did not apply, allow rules did not match (including the shipped example request.client.ip startswith 10.0.), and allow rules with a negated operator such as ne or notin admitted the identities they were meant to exclude. Values are now kept as written. Workaround before upgrading: use a symbol operator without spaces, such as subject.principal.id=alice.smith@example.com or request.client.ip^=10.0.; replace in/oneof lists with one rule per value; for notin, join symbol inequalities with and in the same rule, such as subject.principal.id!=alice.smith@example.com and subject.principal.id!=bob.jones@example.com. Write these FleX conditions without outer parentheses; before this release a parenthesised or can silently never match. For a value that contains spaces, use the LDAP form and write each space as \20, such as where = "(subject.principal.id=alice\\20smith.jones)".
  • Wrong issuer errors stay readable. When a discovery document names a different issuer than configured, Scribe keeps the actual and expected values in the error while escaping control characters and shortening an unusually long actual value.
  • Keep database passwords out of connection addresses. Database passwords given inside database.url, database.host or POSTGRES_HOST can appear in debug logs of the connection pool; set them through database.password or POSTGRES_PASSWORD instead. 3.4 removes them from logs.

Fixed

  • Forwarded LDAP sign-ins keep their own directory account. When a client signed in through a SASL bind, or through any bind with channels.ldap.auth.enabled = false, and Scribe then lost its directory connection for that client, Scribe opened a new connection with its own backend account and ran the client’s later requests there. Later requests that need that directory connection now get UNAVAILABLE until the client binds again, and a write is still never sent twice. Sessions signed in by Scribe itself reconnect as before. See Proxy Authorization.
  • Bearer sign-in survives key-endpoint outages. Bearer tokens signed with the last good keys keep validating when the identity provider’s key endpoint is unavailable or its answer cannot be read, instead of failing after about 20 minutes with the default refresh interval. Entries Scribe cannot read are ignored when the answer also contains a usable signing key. Failed key fetches keep their retry delay. Valid answers retire withdrawn keys within four refresh intervals after the last answer containing them, plus any pending retry delay (up to 60 seconds), including removal of all signing keys and longer cache lifetimes.