Version History
- Changes
Read the outcomes and fixes in this release.
- Upgrade
Check migration guidance before changing an existing deployment.
Find the relevant version below and check breaking changes before scheduling an upgrade.
Next: Upgrade guidance
Version v3.3.0 (2026-10-03)
Security
- Oversized HTTP requests are refused early — BREAKING: HTTP requests with a body larger than 1 MiB are now refused with
413or a closed connection, and sign-in form posts larger than 16 KiB get413— clients that send larger GraphQL or MCP requests now fail. Migration: raisehttp.request-limits.max-payload-size(SCRIBE_HTTP_MAX_PAYLOAD_SIZE) for the socket that needs it, or set it to-1to remove the limit. Earlier releases accepted HTTP request bodies of any size before sign-in, so a single client could make the server reserve large amounts of memory. See HTTP request limits. - Configuration view hides secrets reliably — BREAKING: the configuration view (
/observe/config) and hint details requested withredact=falsenow require Observe write access (by default theadminrole), so signed-in accounts without it now get403; the configuration view and--printconfignow print formatted JSON instead of HOCON. Migration: give operators who need these views the role named inmonitoring.observe.write.auth.rules, or adjust those rules; update scripts that parse--printconfigor/observe/configoutput as HOCON. Previously both showed comments from the configuration files, numeric and true/false values under secret settings, and custom header values such as exporter API keys, so such a secret could be read by any Observe user. They now show no comments and redact every value under a secret setting and every header value, and the view is no longer cached by browsers. The Observe MCP endpoint now followsmonitoring.observe.auth.rules; when it runs on its own socket,monitoring.mcp.auth.rulesreplace them if set. All 3.x releases up to and including 3.2.1 are affected. See Endpoints. - LDAP token errors protect private details. Bearer sign-in and proxy authorization now keep token, account lookup, and unexpected validation details out of LDAP responses. If the identity provider cannot supply signing keys, requests receive a temporary unavailable response. Operators can find the cause in service logs.
- Local account passwords stay local. Alternate directory name spellings now resolve to the configured local account, so an incorrect password cannot be sent to the directory.
- Sign-in redirects stay within allowed pages. Encoded parent-directory segments can no longer move a sign-in redirect outside its allowed page area.
- Signing out over HTTPS ends the session. Signing out over HTTPS left the session cookie in the browser, so the session stayed valid there until it expired. Sign-out now removes it. All 3.x releases up to and including 3.2.1 are affected. No configuration change is needed.
- Other websites cannot change your session — BREAKING: sign-in and sign-out POST requests without origin information are rejected, and plain-HTTP deployments and older browsers such as Safari before 16.4 need the reverse proxy to report the public address — scripts that post the sign-in form without an
Originheader, and those deployments and browsers behind a reverse proxy that does not, now get “Invalid request” instead of a session. Migration: switch scripts that post the sign-in form to HTTP Basic; for plain HTTP or older browsers behind a reverse proxy, enablehttp.requested-uri-discovery, list the connection peer as trusted, and have it sendForwardedwithprotoandhost, orX-Forwarded-For,X-Forwarded-Proto, andX-Forwarded-Host. Another website could submit the sign-in form with an account of its choosing and sign a visitor’s browser into that account without the visitor noticing. The sign-in page now accepts a form only from its own pages; a form posted from elsewhere shows “Invalid request” and creates no session. Over HTTPS, sign-in behind a reverse proxy keeps working in current browsers without configuration changes. Sign-out now rejects cross-site requests and requests without origin information, leaving the current session in place; the in-app sign-out still works, and says so when a sign-out is rejected instead of returning to the sign-in page. Scripts that post the sign-out form without anOriginheader now get “Invalid request”. HTTP Basic, OIDC sign-in, and LDAP bind are not affected. All 3.x releases up to and including 3.2.1 are affected. See Sign-in form protection. - Proxy authorization now takes effect — BREAKING: an LDAP request with a Proxy Authorization control is now checked, and when IdentityScribe forwards it to the directory it runs as the requested identity instead of the signed-in account — a client that names a DN or username without permission, or presents a bearer token that maps to no directory account, now gets
AUTHORIZATION_DENIED(123); a non-critical, repeated, or malformed control getsPROTOCOL_ERROR(2), and a bind with an otherwise valid control getsUNAVAILABLE_CRITICAL_EXTENSION(12); a local account without the permission gets 123 for the control on every operation except a bind, which gets 2 or 12 like any bind; and an abandon request carrying the control is ignored. Migration: list each account that may act for other users inchannels.ldap.proxy-authorization.allowed(for the Identity Hub listener,channels.identity-hub.proxy-authorization.allowed) and make sure IdentityScribe’s directory account may act for those users in the directory; setproxy-authorization.enabled = trueon a local account that should do the same; remove the control from clients that do not need it and from bind requests. Earlier releases ignored the control, so such requests ran with the signed-in account’s directory rights rather than the requested user’s. IdentityScribe now decides before it looks up the requested identity or contacts the directory: abearer:token proves its subject and needs no permission where the listener accepts bearer sign-in, while a DN or username needs the new permission, which no account has by default and which a SASL sign-in gets only when the directory reports the signed-in account. Searches, writes, and other operations forwarded to the directory then run as the requested identity, and Who-Am-I reports it; searches answered from IdentityScribe’s own data and channel access rules still use the signed-in account. A paged or virtual list view search continues only as the identity that started it. Local accounts keep rejecting the control unless they opt in. All 3.x releases up to and including 3.2.1 are affected. See Proxy Authorization. - SASL binds are off by default — BREAKING: the LDAP listeners now refuse every SASL bind with
AUTH_METHOD_NOT_SUPPORTED(7) unless its mechanism is listed, and with channel authentication on a listed mechanism counts as a directory sign-in: it needsldapin the listener’sauth.methods, the account the directory reports through Who-Am-I (RFC 4532) must lie underauth.ldap.baseand matchauth.ldap.filterand must not be a local account’s DN, its roles come fromauth.ldap.roles, SASL binds that cannot reach the directory count toward detecting an outage, and while directory sign-ins fail fast during an outage a new SASL bind fails fast too, unless it is the sign-in let through to check the directory, which IdentityScribe checks before forwarding the bind — a SASL bind whose account the directory does not report, or reports outside that base or filter or as a local account’s DN, fails withINVALID_CREDENTIALS(49). Migration: SASL binds through IdentityScribe are off by default; list the mechanisms you use inchannels.ldap.sasl.mechanisms(for the Identity Hub listener,channels.identity-hub.sasl.mechanisms), make sure the directory answers Who-Am-I for them, and move clients that useEXTERNAL, which can no longer be enabled, to another mechanism or a simple bind. Earlier releases forwarded every SASL bind and took the account from the name in the bind request, which SASL does not check, so a client could sign in with its own credentials and be treated as another account; anEXTERNALbind authenticated IdentityScribe’s own directory certificate. A paged or virtual list view search started while a multi-step SASL bind was in progress no longer continues after the bind completes. All 3.x releases up to and including 3.2.1 are affected. See SASL binds. - LDAP sign-ins need a directory account — BREAKING: an LDAP bind that names no directory account now fails with
INVALID_CREDENTIALS(49): adn:bind whose value is not a DN, and a bearer oru:bind whose token or username maps to no DN — such clients can no longer sign in. Migration: bind with the account’s full DN (dn:uid=alice,ou=people,dc=example,dc=com) or its username (u:aliceor the plain name), and configureauth.ldapso bearer and username binds find the account’s DN. Earlier releases signed such a client in without an account, and requests IdentityScribe forwarded to the directory for it ran with IdentityScribe’s own directory rights. All 3.x releases up to and including 3.2.1 are affected. See Authentication. - Refused LDAP binds leave nothing signed in — With
channels.ldap.auth.enabled = false, a bind the directory accepted but whose account IdentityScribe could not determine, such as an Active Directory user principal name, was refused, yet the client’s later requests on that connection still ran with that account’s directory rights. They now run as an anonymous client, as after any refused bind. All 3.x releases up to and including 3.2.1 are affected. - Oversized LDAP requests are refused — BREAKING: the LDAP listeners now disconnect a client that sends a request larger than 10 MiB — a client that writes larger entries or modifications through IdentityScribe now loses its connection. Migration: if your clients send larger requests and the directory accepts them, raise
channels.ldap.max-message-size-bytes(for the Identity Hub listener,channels.identity-hub.max-message-size-bytes), or set it to0to remove the limit. Earlier releases accepted requests of any size, from clients that had not signed in too. Passwords and SASL credentials larger than 64 KiB, bind DNs and usernames larger than 8 KiB, and bind request controls larger than 8 KiB in total now getINVALID_CREDENTIALS(49) before IdentityScribe contacts the directory, which would drop such a request; Kerberos tokens andbearer:tokens up to 64 KiB still fit. All 3.x releases up to and including 3.2.1 are affected. See LDAP Channel. - JSON parsing receives security fixes. Updated the bundled JSON library with fixes for denial-of-service and deserialization issues. No configuration change is needed.
- Web server receives security hardening. Updated the web server with security fixes for request handling. No configuration change is needed.
Added
- Sign-ins fail fast during directory outages — When the directory stops answering or repeatedly returns busy or unavailable, LDAP sign-ins that need it no longer wait for the ten-second timeout. After five failed sign-in checks in a row, IdentityScribe checks the directory itself; when that check fails too, sign-ins fail immediately with LDAP result 52, HTTP 503, or “Sign-in temporarily unavailable” on the login page, and every ten seconds the next sign-in first checks whether the directory answers again. Sign-ins that fail because of what a client sent, such as wrong passwords or credentials larger than the directory accepts, never make other sign-ins fail fast. Normal sign-ins resume without a restart. Sign-ins rejected this way are counted instead of logged one by one, so clients that retry during an outage do not flood the log. Local accounts, browser sessions, cached sign-ins, and searches are not affected. Adjust or turn this off with
auth.ldap.breaker.threshold,auth.ldap.breaker.open-duration, andauth.ldap.breaker.enabled; see Authentication. - Doctor reports directory sign-in outages — The new
auth.ldap.upstreamdoctor check and thescribe_ldap_upstream_stategauge show whether the directory answers sign-ins: degraded when sign-in checks fail more often than usual, critical while sign-ins fail fast. Readiness is intentionally unchanged, because the directory serves every instance and taking them all out of rotation would not help. See Monitoring. - Release archives include third-party attribution. The release archive now contains
THIRD_PARTY_LICENSES.mdwith the notices and license texts for its open-source components. - Readiness reports stalled searches —
/readyzand/healthznow return503while searches are stalled: every query permit is in use, a search has waited for a permit or was turned away since the last release, and no permit has been released for 60 seconds. A turned-away search still counts after it gave up. A stalled instance usually needs a restart, so an orchestrator can now take it out of rotation; if a search finishes after all, the stall ends and the probes return200without one. A busy instance whose searches keep finishing stays ready, and/livezis unchanged. The newquery.permit_stalldoctor check andscribe_query_permit_stall_secondsgauge report the stall, and the log records aquery_permit_stallwarning when it starts andquery_permit_stall_clearedwhen it ends. If you restart, collect a thread dump withkill -3first. Tune the wait withmonitoring.readiness.query-stall-after(SCRIBE_MONITORING_READINESS_QUERY_STALL_AFTER), or keep readiness independent of searches withmonitoring.readiness.fail-on-query-stall = false(SCRIBE_MONITORING_READINESS_FAIL_ON_QUERY_STALL=false).
Changed
- LDAP StartTLS setting now rejected — BREAKING: IdentityScribe refuses to start when
start-tlsorssl.insecureis set totruefor an LDAP connection — configurations with either setting in any LDAP block now fail at startup. Migration: switch toldaps://(usually port 636) and setldap.ssl.caif your directory uses a private CA. The production guide previously suggestedldap.start-tls = true, but this setting was never applied, so the directory connection stayed unencrypted. See Production guide. - Faster planning choices adopted more often. Repeated searches switch to a consistently faster planning choice more often when response times vary. A choice that is slower for typical searches is no longer adopted only because its slowest searches finish sooner.
- Environment variables override the configuration file — BREAKING: environment variables listed in the configuration reference now take precedence over values in the configuration file — a stale variable left in a service unit or container environment now wins over the file, for example pointing the service at an old database or directory, and a variable the service previously ignored or read leniently now stops startup when invalid, such as an OTLP exporter timeout, an on/off value like
1orTRUE, or an invalid duration or number; an invalid OTLP protocol stops startup when that exporter is enabled. Migration: before upgrading, list the environment variables the service receives from service units, container definitions, and shell profiles; remove any that should not apply; usetrue,false,yes,no,on, orofffor on/off settings and valid durations, numbers, and OTLP settings; after upgrading, check theconfig_env_overridestartup warning, which names the settings an environment variable changed without showing values. Empty variables count as unset, and list settings keep their comma- or space-separated form, such asSCRIBE_AUTH_METHODS=bearer,ldap. Object settings such asSCRIBE_LDAP_VIRTUAL_ATTRIBUTESnow accept a value like{}even without a file value.SCRIBE_LICENSE_FILEand thePOSTGRES_HOST,POSTGRES_PORT,POSTGRES_USER, andPOSTGRES_PASSWORDfallbacks are unchanged: a value in the configuration file still wins. The--licensecommand-line option and alicense.fileJava system property now take precedence overlicense.filein the configuration file; previously the file value won, so remove a stale--licensefrom service units before upgrading. See configuration precedence and upgrading to v3.3.0.
Fixed
- Startup failures consistently signal failure — IdentityScribe now always ends with exit code
1when it gives up starting, including when a required setting such asauth.session.cookie-keysis missing and every retry fails; this case used to end with0. Docker restart policies, systemd and Kubernetes now see such a start as failed and can restart or alert. An HTTP port that is already in use now also fails startup: IdentityScribe retries according toretry.servicesand ends with exit code1if those attempts are exhausted, instead of running without health checks, metrics, APIs or the admin UI. A requested stop is not affected. - Slower planning choices reverted sooner. Recent measurements help repeated searches return sooner to the standard planning choice when an adopted choice becomes slower.
- Rare search and shutdown hangs fixed — IdentityScribe is now built on Java 25.0.4 (GraalVM Community Edition 25i2). Earlier releases were built on Java 25.0.2, where a task waiting with a timeout could, rarely, miss the signal to continue and wait forever, so a search, sign-in, or shutdown could hang until restart. The release binary contains its Java runtime, so installing this release is all you need to do. If you build IdentityScribe from source, use GraalVM Community Edition 25i2 (Java 25.0.4) or later.
- Faster totals for broad either-or searches — The exact total of a search for one of several values or prefixes on different attributes, such as
(|(givenName=Mara)(cn=Mara)), could take about twice as long as needed when it matched many entries and IdentityScribe had not yet learned how many entries each part matches, and the estimated total stayed at 200 whatever the real count. These totals are now computed the standard way in that case. All 3.x releases up to and including 3.2.1 are affected. No configuration change is needed. - Sorted contains searches tune themselves. Contains searches sorted by the searched attribute now record their timings like other searches, so adaptive planning can pick a faster choice for them and Query Diagnostic Reports show them.
- Backward paging returns the previous page. Fixed a case where paging backward with a
beforecursor through a search sorted by a single-valued attribute returned entries far from the cursor instead of the previous page, and placed entries without the sort attribute on the wrong side of it. No configuration change is needed. - Sorted paging retains missing values. Fixed a case where cursor paging omitted entries without the sort attribute after a page ended on an entry with a value, when moving forward in ascending order or backward in descending order. No configuration change is needed.
- Grafana monitoring bundle starts reliably — The Docker full stack in the monitoring bundle now starts its PostgreSQL 18 database and serves the monitoring endpoints on port 9001 that the health check and Grafana dashboards use. The bundle reads the LDAP source, the entries to sync, your license file and a session key for the Operator UI from a
.envfile, and can publish its database on another port when one on your host already uses 5432; see Grafana monitoring bundle for the prerequisites. Building the full-stack image yourself currently needs an x86_64 host. A database volume that holds data from another PostgreSQL major version needspg_upgradeor a dump and restore. - Late deletes preserve replacement entries. A delayed deletion for a removed entry no longer removes a new entry created under the same name.
- Forwarded requests explain directory outages. If a forwarded LDAP request cannot open a directory connection, it now returns
UNAVAILABLE(52) with a plain message. New forwarded binds and writes previously returned 80; a first forwarded search could return a different connection code. Unexpected search failures also keep private details out of the response. - Dropped directory connections answer consistently. If the directory connection behind a forwarded LDAP request drops during a session and cannot be reopened, searches, binds, writes and other forwarded operations now return
UNAVAILABLE(52) with “The directory is temporarily unavailable.”, the same answer as when no connection can be opened. They previously returnedSERVER_DOWN(81) or another client-side code such as 85 or 91, with connection error text that could name the directory host. - Error reference shows actual messages. The error reference now lists the messages clients can receive for token, export, lookup, and GraphQL failures, plus a search that fails a consistency check, in place of generic text.
- Large legacy upgrades finish rebuilding — A startup rebuild when upgrading from 1.x could fail repeatedly on a large directory with the default database settings. These rebuilds now complete without increasing the database lock-memory allowance. Upgrades from 3.2 do not run this rebuild.
- Shared instances recheck sorted searches — Instances sharing a database now stop using affected sort indexes during startup rebuilding and verify them again afterwards. New installations and upgraded instances resume normal sorted-search performance after verification without false backfill alerts. The convergence view shows when the readiness check is paused instead of reporting progress that it cannot verify. Upgrades from 1.x still require a maintenance window. See Upgrading.
- Sorted searches with totals succeed and run faster — A sorted search that asked for the total number of matches could fail instead of returning results: LDAP paged searches returned result 19 (constraint violation) with “Can’t do that right now”, REST returned HTTP 409, and GraphQL and MCP returned an error. This affected first pages that request only the total or name a virtual attribute among the requested attributes, for two kinds of filter on the sort attribute: a lower bound such as
(sn>=M)sorted bysn, and a prefix such as(cn=Mei*)sorted bycnthat matches more than 10,000 entries of one type, from the second such search on. These searches now return their entries with the exact total, and their exact and estimated totals are computed the same way as for the search without sorting, so they take about as long and estimates are as close. All 3.x releases up to and including 3.2.1 are affected. Totals for other sorted searches are faster as well: in our benchmarks on a directory with 250,000 entries, they were typically about three times faster than in 3.2.1, and up to about 20 times faster for broad filters on an attribute other than the sort attribute, such as a “starts with” search on a common first-name prefix sorted by surname. Totals for sorted searches that match only a few entries were already fast and stay that way. No configuration change is needed. - Debug logging reaches every log category —
--debug,--trace, and a debug or tracelog.levelorSCRIBE_LOG_LEVELnow also apply to theSuperVisor,Ingest,Monitoring,License, andConfiglog categories, which stayed atinfobefore. A quieter global level, such as--quietorlog.level = warn, still keeps their operation logs atinfo. A level set for one category, such asSCRIBE_LOG_MONITORING=warn, still wins in both directions. See Logging. - Library log levels can be changed —
SCRIBE_LOG_KENOXA,SCRIBE_LOG_HIKARI,SCRIBE_LOG_FLYWAY,SCRIBE_LOG_JOSE4J, andSCRIBE_LOG_HELIDONhad no effect, and neither did a quoted key such aslog."com.zaxxer.hikari"in the configuration file, so these libraries always logged atwarn. The variables now apply. In the configuration file, write the setting without quotes, as inlog.com.zaxxer.hikari = debug; settings already written that way keep working. If one of these variables is set in your environment, the library now logs at that level. See Logging. - LDAP synchronization settings take effect —
ldap.checkpoint-offset,ldap.idle-period,ldap.ignore-checkpoint-timestamp, andldap.single-value-attributes, set in the configuration file or throughSCRIBE_LDAP_CHECKPOINT_OFFSET,SCRIBE_LDAP_IDLE_PERIOD,SCRIBE_LDAP_IGNORE_CHECKPOINT_TIMESTAMP, andSCRIBE_LDAP_SINGLE_VALUE_ATTRIBUTES, were ignored, so synchronization always used the built-in values and the directory schema alone. They now apply. If you setldap.ignore-checkpoint-timestamp = true, every start now runs a full synchronization; remove it unless that is intended. If you setldap.single-value-attributes, check that the listed attributes hold one value in the directory. See LDAP. - Maintenance and reconciliation thresholds take effect —
database.maintenance.soft-thresholds,database.maintenance.hard-thresholds,ldap.reconciliation.soft-thresholds, andldap.reconciliation.hard-thresholds, set in the configuration file or through their environment variables, were ignored, so maintenance and reconciliation always used the built-in thresholds. They now apply, and a configured set of thresholds replaces the built-in one. If you set them, check that the values still describe how idle the system must be before maintenance or reconciliation runs. See Database and LDAP. - Duplicate local account aliases rejected — Two local accounts whose
usernamealiases differed only by surrounding spaces or invisible characters, or an alias that was another account’s DN with such padding, passed configuration validation, and the alias then signed in as nobody. Such a configuration is now refused at startup with a clear message, as is an alias that consists only of padding. Configurations with distinct aliases are not affected. - Trusted proxy address ranges now work — BREAKING:
http.requested-uri-discovery.trusted-proxies.exactnow matches CIDR ranges and IPv6 address spellings by address, and rejects non-IP entries at startup — a host name that was previously ignored can now prevent startup. Migration: replace non-IP entries with IP addresses or CIDR ranges; move any intended pattern over the peer IP address tohttp.requested-uri-discovery.trusted-proxies.pattern. - Reverse proxies report the public address — BREAKING: with trusted
X-Forwarded-*headers, IdentityScribe now uses the public address for sign-in origin checks, CORS, OIDC redirect URIs, and OAuth metadata — OIDC sign-in fails at the identity provider when the redirect URI registered there uses the internal orhttp://address. Migration: register the public HTTPS redirect URI at the identity provider. See Sign-in form protection. - CORS accepts standard web origins. With
http.cors.allow-origins = [same-origin], requests to HTTPS port 443 or HTTP port 80 now match the browser’s origin. Thehostvalue ofhttp.cors.allow-originsreturns the same address without an unnecessary default port. - OIDC sign-in works over HTTPS — OIDC sign-in failed with “CSRF validation failed” whenever IdentityScribe received the sign-in over HTTPS, because browsers discarded its temporary verification cookie. The cookie is now accepted and removed after sign-in, and the new session cookie is kept. All 3.x releases up to and including 3.2.1 are affected. No configuration change is needed.
- MCP lookups reject bad input clearly. Reference searches now ignore surrounding spaces and keep long misses concise. Unknown help topics return a validation error that lists the accepted topics. The hint shown with invalid-argument errors now points to a help topic and a reference search that work.
- Sign-in and sign-out reach any page. Redirects after sign-in and sign-out now work when the destination page or its query contains non-ASCII characters, such as umlauts.
- Directory outages show temporary sign-in failure — When the directory cannot be reached or returns busy or unavailable, the sign-in page and every authentication channel now report a temporary failure instead of wrong credentials. LDAP bind returns 52 and HTTP requests return 503. Local account sign-ins remain available during a directory outage.
- Early stream closes respect concurrency limits — When a client closed a search result stream before reading it to the end, the service could let more searches reach the database at once than the configured maximum, adding load to an already busy instance. Early stream closes now stay within the limit on every channel. All 3.x releases up to and including 3.2.1 are affected, and no configuration change is needed.
- Numeric local account DNs recognised — A configured local account is now recognised when its login DN is presented with numeric attribute types, such as
2.5.4.3=proxy,o=globalforcn=proxy,o=global, on all channels (browser login, HTTP Basic, and LDAP bind). Earlier releases treated that spelling as an unknown name and forwarded it with the submitted password to the directory, so a directory entry at the same DN could sign in even though the DN belongs to a local account. Local accounts were introduced in 3.2.0, so 3.2.0 and 3.2.1 are affected. As with the named form, a local account signs in only with its configured password, and a wrong password is never tried against LDAP. No configuration change is needed. - Database environment variables no longer block startup — Setting nested and some other
database.*options by environment variable, such asSCRIBE_DATABASE_FILTER_SELECTIVITY_PLAN_MODE_ENABLED=false,SCRIBE_DATABASE_ORPHANED_TRANSCRIBES_BEHAVIOR=ignore, orSCRIBE_DATABASE_QUERY_HTTP_ACQUISITION_TIMEOUT=10s, now takes effect. Previously the service refused to start with anUnsupported property nameerror. No configuration change is needed. - Busy searches no longer disrupt synchronization — Under heavy search load while the database was slow to write, saving query diagnostic report details could occupy every connection that synchronization needs. Searches then waited up to 30 seconds, synchronization logged “Failed to persist entry/event” and re-read entries from its last checkpoint, and the log filled with “Failed to persist query diagnostic snapshot” warnings. Report details are now saved in the background, one query at a time, and only while a connection beyond those synchronization needs is free; otherwise they are skipped instead of waiting, and a save that takes longer than two seconds is abandoned. Synchronization needs one connection per transcribe, at least two. If
database.system-pool-sizeis set to exactly that, report details are not saved and a warning at startup says so; raise it by one to save them. While the database is busy, only the latest details of each query are kept, and if more queries wait to be saved thanmonitoring.hints.cache.sizeallows, the others are skipped. Skipped details are not retried automatically; they may still be saved when the current query completes or when the query runs again, if there is room. The log records one warning when skipping starts, and one with the skipped count and the time of the last skip on the first save at least a minute after that skip, or at shutdown if skipping had not ended by then. A database that stays near its limit logs at most one such pair per minute. All 3.x releases up to and including 3.2.1 are affected. No other configuration change is needed. - Sorted searches recover after first start — After the first start on a new database, sorted searches could keep using a slower plan until the next restart, and
/observe/convergencereported sort indexes as ready while none were being tracked. Sort indexes are now rebuilt during that start and become ready on their own, and the convergence report counts them as backfilling until they are. All 3.x releases up to and including 3.2.1 are affected. No configuration change is needed. See Deployment verification. - Adaptive planning stays active continuously. Searches no longer fall back to the standard planning choice at regular intervals while the database responds normally, including during quiet periods. Turning adaptive planning off takes effect promptly even after a clock correction, and still lets searches already running finish.
- License checks ignore system language — BREAKING: the directory product is now identified the same way under every system language — an installation that runs under a Turkish or Azerbaijani system language with an UnboundID or Ping Identity directory fails to start with
Invalid scopesuntil its license is reissued. Migration: on such an installation, send the license request the upgraded service shows, as described in Renewing a License. Under those system languages, such a directory was identified under a different product name, so a license requested under one system language failed withInvalid scopeswhen the service started under another. On such an installation, the first start after the upgrade also runs one full synchronization of every entry type. Other installations keep their license and synchronization state. - A stop during startup ends cleanly — A stop that arrived just as the service, the synchronization of a transcribe, or an LDAP listener was starting, or restarting after an error, could leave it marked as failed, and the shutdown then logged an error although nothing had started. Such a stop now ends cleanly. No configuration change is needed.
- Forwarded virtual list view searches work — Every virtual list view (VLV) search that IdentityScribe forwards to the directory, such as a search below
ldap.ignore-contexts, failed with “Paging or VLV continuation is invalid after authentication changed; restart the search.” and was logged as an unimplemented search, even when the client had not signed in again. Identity Hub with VLV paging hit this on every forwarded search. These searches are forwarded again, and like other first-page searches they now reconnect once when their directory connection has gone stale. Continuing a paged or VLV result after signing in as another account is still rejected. A VLV request with a malformed control, and any request with a control whose type is not a plain numeric object identifier such as2.16.840.1.113730.3.4.9, is now answered with a protocol error, and a search rejected this way tells the client why. 3.2.0 and 3.2.1 are affected. No configuration change is needed. - Multi-value lookups report correct totals — A search for any of several values of an attribute listed under
value-match, such as(|(workforceID=A)(workforceID=B)), returned the matching entries but reported a total of 0 in LDAP paged results and virtual list view responses. Exact and estimated totals for such searches on the REST, GraphQL, and MCP channels were wrong as well. Identity Hub 9.13 and earlier rely on that total in their default paged search and therefore returned no results; later Identity Hub releases returned the entries but could report a total of 0. Such searches now report the number of matching entries. All 3.x releases up to and including 3.2.1 are affected. No configuration change is needed.