> ## Documentation Index
> Fetch the complete documentation index at: https://docs.strata.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026

**October 19 2026**

## Recover from expired upstream credentials without restarting your AI agent

When an MCP tool call fails because the user's upstream credential has expired or been revoked, the AI Identity Gateway now tells the user how to fix it. Previously the tool call returned a generic `internal server error`, and the only way to recover was to sign out and start a new session.

Now the tool result includes a sign-in link that the AI agent shows to the user. The user opens the link in their browser, signs in again to the affected identity provider only, and returns to their agent. Their next tool call succeeds in the same session.

To turn this on, set the new `mcpProvider.reAuthCallbackURL` option on the AI Identity Gateway and add the same URL to the gateway's OIDC Provider client. This option is available in YAML configuration only. The Maverics Console cannot set it yet. See [Recover from expired upstream credentials](/guides/ai-identity/mcp-proxy#recover-from-expired-upstream-credentials) for setup steps.

### MCP Provider

* Return a sign-in link when the OIDC Provider rejects the token exchange for a tool call because the user's upstream credential has expired or is missing. The link is marked for display to the user, so MCP clients that support annotations show it directly.
* Return the same sign-in link when an upstream MCP server rejects a tool call with HTTP 401, which happens when the upstream service revokes a credential that the token exchange still returned.
* Add a re-authentication landing page. After the user signs in, the identity provider redirects them to this page, which confirms that sign-in succeeded and tells them to return to their agent. The gateway serves the page at the path of the new `mcpProvider.reAuthCallbackURL` option. If the option is not set, tool errors do not include a sign-in link.

### OIDC Provider

* When an authorization request includes a `login_hint` that matches a passthrough token brokering audience, sign the user in to that audience's connector only, even if they already have an active session. This refreshes the one expired upstream credential without signing the user in to every connector again. A `login_hint` that matches no passthrough mapping returns an `invalid_request` error.

**September 30 2026**

## FIPS 140-3 Compliant Orchestrator Builds Now Available

You can now download FIPS 140-3 compliant builds of the Maverics Orchestrator. They use the Go Cryptographic Module v1.0.0 (CMVP certificate #5247), a FIPS 140-3 Level 1 validated module, running in its approved mode. These builds are meant for federal agencies, defense contractors, and other organizations that must use FIPS-validated cryptography.

**How to get it:** In the Maverics Console, open any Deployment and select **Download Orchestrator Software**. The **FIPS 140-3 Compliant Build** section is below the standard platform installers. After you download the archive, check it against the SHA-256 checksum shown in the modal.

**What's included in maverics-orchestrator\_fips.zip:**

* Orchestrator binaries for Red Hat and Ubuntu
* Container image tarball
* FIPS 140-3 Compliance Guide (PDF)

The FIPS build uses the same package name, install path, and service unit as the standard build.

> [!NOTE]
>
> **Scope:** The FIPS 140-3 compliance claim covers only the Orchestrator data plane. It does not cover the Maverics Console.

### Additional Changes

* **OIDC Connector:** Add a typed `TokenBrokeringError` for authorization server rejections during token brokering, enabling more precise error handling in connectors.
* **Connectors:** Forward custom query parameters to the Auth0 authorization request.

**September 22 2026**

* **FIPS:** Initial FIPS 140-3 support. Build not yet available to download.
* **OIDC Connector:** Add `errorHandling` configuration to the OAuth connector, covering additional error cases in the callback handler.
* **Proxy Apps:** Include the request path in HTTP access logs to support filtering of health-check traffic.
* **SAML Provider:** Reject invalid SP signing keys or key pairs at configuration load time.
* **OIDC Provider:** Return `invalid_grant` for refresh token reuse and client mismatch.

**September 15 2026**

Changes to support for FIPS 140-3. This build is not yet available to download.

**September 11 2026**

Changes to support for FIPS 140-3. This build is not yet available to download.

**September 4 2026**

* **OAuth Connector:** Accept `expires_in` as a quoted string in token responses, fixing compatibility with identity providers that return the field as a string value rather than a number.

**September 2 2026**

* **OAuth Connector:** Fix scopes not being sent during dynamic client registration.

**August 27 2026**

* **OIDC Connector:** Add [RFC 7591 Dynamic Client Registration](/reference/orchestrator/identity-fabric/oauth#dynamic-client-registration) support. OIDC connectors can now register with identity providers dynamically, removing the need to pre-configure a static client ID and secret when the IdP supports Dynamic Client Registration.
* **OIDC Connector:** Add [Client ID Metadata Document (CIMD)](/reference/orchestrator/identity-fabric/oauth#client-id-metadata-document) support. OIDC connectors can now authenticate using URL-based client IDs, with the connector fetching and validating the Client ID Metadata Document at runtime.
* **OPA:** Add `jwt.parse_bearer` built-in function for Rego policies. Policies can now parse and inspect JWT bearer tokens directly without a service extension.
* **MCP Provider:** Fix intermittent tool listing failures when multiple concurrent requests were in-flight simultaneously.

### Security Improvements

### Proxy apps

* Authorization policy is now evaluated against the same normalized request path that is forwarded upstream, giving consistent policy matching for URLs that contain encoded characters or path parameters.
* The mutual-TLS host guard now normalizes the Host header (case and port) before matching a request to its virtual host, so requests are consistently associated with the intended host configuration.

### OIDC Provider

The form\_post authorization response now HTML-escapes the redirect URI when rendering the auto-submitting form, ensuring redirect URIs containing reserved characters are handled correctly.

**August 14 2026**

### Feature Deprecations

The following features have been removed from the Orchestrator and are no longer supported:

* (Experimental) Orchestrator Clusters
* LDAP Provider: Remove SASL, GSS-SPNEGO, and NTLM authentication mechanisms

### Enhancements

* OIDC Provider: Add support for complex types in access token claims mapping
* OIDC Provider: CIMD apps now only issue refresh tokens when explicitly requested and when administrator-enabled

**August 6 2026**

### Bug Fixes

* **Config:** Pre-flight config validation prevents startup loop. The Orchestrator now validates configuration before starting up, preventing a bad config from causing a crash-restart loop. Invalid configurations are rejected at startup with a clear error instead.
* **MCP Proxy:** MCP tools list correctly handles unreachable upstreams. list-tools calls no longer fail when one or more upstream MCP servers are unreachable. Available tools are returned from reachable upstreams while unreachable ones are skipped gracefully.
* **MCP Provider:** `WWW-Authenticate` header uses absolute URL for `resource_metadata`. The `resource_metadata` field in `WWW-Authenticate` challenge responses now correctly returns an absolute URL, fixing compatibility issues with MCP clients that use it to locate the protected resource metadata document.
* **OIDC Provider:** Access token claims mapping applied to CIMD clients. `accessToken.claimsMapping` configuration is now correctly applied when issuing tokens to OIDC CIMD apps. Previously, claims mapping was accepted by the config but silently ignored for CIMD clients.

**July 30 2026**

* **OIDC Provider:** Add support for claims mapping for access tokens
* **OAuth Connector:** Improve login callback validation and avoid unnecessary JWKS fetches during authentication
* **OIDC Connector:** Fix PKCE generation to exclude special characters

**July 27 2026**

* **MCP Provider:** Reconcile proxied tools per session, ensuring MCP clients see a consistent and current tool list throughout a session.
* **Orchestrator:** Add support for graceful process restarts, reducing downtime during config changes and enabling everything except ports to be updated without a full restart.

**July 22 2026**

* **OIDC Provider:** Refresh upstream access tokens during passthrough token brokering
* **Licensing:** Updated terms and conditions URL in startup event log to point to the current Rubrik–Strata service agreement

**July 17 2026**

* **Authenticate Service Extension:** Add `idfabric.WithForceAuthentication()` support. When called from `authenticateSE`, the connector is instructed to actively re-authenticate the user with the IdP even if an existing session is present. The SAML connector is the first to implement this, sending `ForceAuthn="true"` on the AuthnRequest. See the [documentation](/reference/orchestrator/service-extensions/proxy#force-re-authentication-on-every-login) for configuration details.
* **MCP Proxy:** Add OPA-based tool listing control via a new `listing` authorization block. The policy is evaluated once per tool in every `tools/list` response from the upstream server; only tools where the policy returns `allowed=true` are forwarded to the client. Policies evaluate against upstream tool names before namespace prefixing, keeping them consistent with `inbound` call-time policies. See the [documentation](/reference/orchestrator/applications/mcp-proxy#tool-filtering-opa) for configuration details.

**July 14 2026**

## \[Experimental] Client ID Metadata Documents (CIMD)

The Orchestrator now supports dynamic OAuth client registration via URL-based client IDs, implementing `draft-ietf-oauth-client-id-metadata-document`. AI agents and MCP clients (Claude Code, ChatGPT) can authorize without being pre-registered — the Orchestrator fetches and validates the client's metadata document at runtime.

Configure using the new `oidcCimd` app type. See the [full documentation](https://docs.strata.io/reference/orchestrator/experimental/client-id-metadata-documents) for configuration reference and examples.

### Security

* Resolved security issues

**July 1 2026**

## Hardened encryption of Redis-cached values

This release strengthens how the Orchestrator encrypts values stored in an external Redis cache. The on-disk format of cached entries has changed as a result.

No action required on upgrade. The Orchestrator adopts the new format automatically. Entries written by earlier versions are ignored and expire on their own TTL if configured with a TTL. You do not need to flush or modify Redis, and no users are signed out — session stores do not use the Redis cache.

**What to expect after upgrading:**

* **OIDC Provider.** Refresh tokens issued before the upgrade are invalidated. Applications re-authorize on their next refresh; for users with an active session this is seamless, with no sign-in prompt. Existing JWT access tokens remain valid until they expire. The transition completes within your refresh-token lifetime (default 24 hours). Clients that authenticate without a user session, such as machine-to-machine clients, may need to re-authenticate once. Existing opaque access tokens will need to be re-issued.
* **SAML Provider.** Flows in progress at the moment of upgrade may need to be retried. Established sessions are unaffected.
* **Service Extensions.** Cached entries from before the upgrade are treated as misses and repopulated on next use. If an extension combines direct key access (disable-prefix) with value encryption, re-write previously stored values, as they are unreadable in the new format.
* **Multi-node deployments.** Complete the rollout promptly. Mixed-version clusters may not share cached entries, causing a temporary rise in re-authentications until all nodes are upgraded.

### Fixes

* **OIDC Provider:** Return HTTP 400 for login callback failures caused by client errors

**June 22 2026**

Internal improvements and maintenance updates.

**June 18 2026**

## Filter MCP tools by access token

MCP Proxy apps can now apply an OPA **connection authorization** policy that decides, per upstream MCP server, whether the gateway connects to it and lists its tools — evaluated against the caller's access token. Instead of surfacing every upstream's tools to every client, you can scope which tools each session sees based on identity.

* **MCP Proxy:** Add OPA policy support for connection authorization, filtering which upstream MCP tools are exposed to a session based on the access token

## Deployments

* **Google Cloud Config Storage:** Add read-only scope and workload identity support for the GCP config provider

### Fixes

* **MCP Provider:** Fix HTTP deadline not being cleared when MCP is enabled, which could cause requests to time out unexpectedly
* **MCP Proxy:** Clean up upstream MCP sessions when the downstream session ends

**June 3 2026**

* **Service Extensions:** Fix configuration bundle asset access for proxy app's `CreateHeader`, single logout's `ParsePostLogoutSE`, and session's `ParseEvalIdleTimeoutSE` and `ParseEvalMaxLifetimeSE` service extensions
* **OIDC Apps:** Allow non-identity-provider namespaces to be used in token brokering exchange template interpolation

**June 1 2026**

* **MCP Proxy:** Fixed token audience validation so a token is accepted when any one of its listed audiences matches an expected value, instead of being rejected unless all audiences matched.
* **MCP Proxy:** Fixed a signature verification issue that could block requests when multiple MCP servers are configured.

**May 28 2026**

* **Token Brokering (experimental):** Add [Federated Exchange](/reference/orchestrator/experimental/token-brokering) flow, where the Orchestrator mints a short-lived JWT and exchanges it with an upstream authorization server (e.g., Databricks, GCP Workload Identity Federation). Mappings also support dynamic claim values via templating interpolation.
* **OIDC Connector:** Add `disableClientAuthentication` for federation flows where the upstream authenticates via the subject token alone (e.g., Databricks account-wide federation)
* **OIDC Provider:** Add support for RFC 7638-compliant JWK thumbprints as the `kid`. Opt in per signing key with `useRFC7638Thumbprint: true` — coordinate with relying parties first, since the `kid` will change.
* **OIDC Client:** Cache the actor token used in `client_credentials`-backed token exchange requests

**May 14 2026**

* **OIDC Provider:** Allow clients with only non-interactive grants to omit authentication
* **Telemetry:** Add support for v1 OTel configuration
* **Security:** Resolved security issues

**April 30 2026**

* **Config:** Fixed `MAVERICS_DEBUG_MODE=true` being silently ignored when a `logger:` block was configured. Setting the env var now correctly forces DEBUG-level logging as documented.

**April 24 2026**

## What's new

**MCP**

Significantly expanded MCP observability so operators can run at info and still get full session traceability and audit coverage — no more flipping to debug to reconstruct what happened.

* Every MCP request log now carries a hashed mcpSessionID, giving you end-to-end correlation across a client-to-Maverics session without exposing the raw Mcp-Session-Id credential.
* Proxy-path logs also carry an upstreamMCPSessionID, so you can follow a single interaction from the client, through Maverics, to the upstream MCP server on the same line.
* Every tool call emits a single tool call completed log at info with an outcome of success, tool\_error, or failed — consistent across bridge and proxy modes.
* Every list-tools call emits a single list tools completed log at info with the outcome and tool count.
* Session register/unregister and upstream session established/terminated events are now surfaced at info.
* Raw session IDs never appear in logs or traces.

### Fixed

**MCP Proxy**

Fixed an issue where responses from upstream MCP servers using gzip compression could reach the client corrupted or unreadable. Compressed responses are now handled correctly.

### Improvements

**Logging**

Audit and security events now log at info level. This makes them visible in standard log pipelines without needing to lower global log thresholds, so your SIEM and observability tooling will pick them up by default.

**April 13 2026**

* **Logout:** Fix bug where logout redirect URLs containing pre-existing query parameters (e.g., Azure B2C custom policy endpoints with `?p=<policy>`) produced malformed URLs with duplicate `?` characters, causing downstream parameters like `id_token_hint` and `state` to be silently dropped

**April 12 2026**

* **MCP Proxy:** Fix path parameter handling and improve tolerance for common schema quirks in MCP bridge apps built from OpenAPI specs

**April 10 2026**

* **OIDC Provider:** Add [token brokering](/reference/orchestrator/experimental/token-brokering) (experimental) to the OIDC provider. Clients can exchange a Maverics access token for upstream service tokens using standard RFC 8693 token exchange. The initial release supports session passthrough mode, which returns a cached upstream token. Token brokering integrates with existing OPA token minting policies for authorization.

**April 9 2026**

* **Telemetry:** Add W3C `traceparent` header propagation to maintain a stable traceID across the entire request lifecycle. When a request enters the Orchestrator, the traceID is preserved and forwarded to all downstream services — including identity providers and MCP endpoints — enabling true end-to-end distributed tracing with a single, consistent identifier. This is especially valuable when the Orchestrator acts as an auth provider to an AI Identity Gateway, where a single user prompt can trigger a chain of token exchanges, policy evaluations, and tool invocations across multiple services. With a stable traceID, operators can trace an AI gateway request from initial authentication through policy evaluation, token minting, and downstream MCP tool calls, correlating every hop in a single distributed trace.

**March 26 2026**

* **SAML Provider:** Make NameID name qualifiers optional
* **SAML Provider:** Fix WS-Fed name claim incorrectly being included in SAML assertions
* **SAML Provider:** Correct XML namespacing across all SAML response types

**March 13 2026**

* **Telemetry:** Add stable Secure Orchestrator ID (`soid`) to all log entries and OTel telemetry (`service.instance.id`) for deployment correlation
* **OIDC Connector:** Add configurable error handling for authentication callbacks
* **OIDC Provider:** Fix state parameter encoding in form post response mode

**March 6 2026**

* **Security:** Resolved security issues

**March 5 2026**

* **MCP Proxy:** Gracefully re-establish session with the upstream MCP server and retry the request when the session is terminated
* **Proxy Apps:** Allow service extensions to be reused across all application types by loosening namespace validation
* **Connectors:** HYPR connector now reads custom HTML files from the configuration bundle

**March 5 2026**

* **MCP Proxy:** Gracefully re-establish sessions with upstream and retry requests when a session is terminated
* **Proxy Apps:** Allow service extensions to be reused across all app types
* **Connectors:** Support reading custom HTML files from the configuration bundle for Hypr integrations

**February 18 2026**

* **TLS:** Add max version configuration for all TLS settings
* **Session:** Fixed an issue where empty sessions were persisted when the SLO endpoint terminated an unestablished session

**February 16 2026**

* **MCP Proxy:** Add configurable scopes and token lifetimes for all MCP protocol operations
* **Security:** Resolved security issues

**February 5 2026**

* **Security:** Resolved CVE-2026-2405
* **MCP Proxy:** Respect outbound authorization policy when making list tools requests

**January 16 2026**

* **SAML Apps:** Enable claims mapping and the BuildClaims service extension to be used together

**January 15 2026**

* **MCP Proxy:** Explicitly handle session termination errors that are returned from the upstream
* **OIDC Connector:** Add client assertion authentication mechanism (rfc 7523)
* **OIDC Connector:** Add support for JWT client assertion authentication as part of the token exchange grant
* **OIDC Provider:** Demonstrate JWT client authentication can be used with authcode, token-exchange grants
* **OIDC Provider:** Make openid scope and scope param optional

**January 8 2026**

* **SAML Provider:** Ensure SAML Response elements are ordered correctly

**January 6 2026**

* **OIDC Provider:** Add Subject and Actor token claims to token minting policy