Skip to content

All versions since v3.3.4 (2026-10-22)

  • 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.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.