Changelog — Enhancement

Edge Components release with faster PostgreSQL and Amazon Redshift connections

October 30, 2026

Aembit has released new versions of the following components and packages:

Agent Proxy 1.35.6254
Aembit CLI 1.35.6254
Agent Injector 1.35.446
AWS Lambda Extension 1.35.199
AWS Lambda Layer 1.35.199
Helm Chart 1.35.575
AWS ECS Terraform 1.35.5

For the latest available versions of these components, see the Edge Components Supported Versions page.

Key Updates:

Faster PostgreSQL and Amazon Redshift connections - When Agent Proxy injects the credential, it passes the connection’s traffic through after the database authenticates the connection. Connections handle more load and use less memory.
PostgreSQL and Amazon Redshift workload events - When Agent Proxy injects the credential, events end at authentication. Otherwise, Agent Proxy now records an event for every message on the connection, as PostgreSQL and Amazon Redshift describes.
Large database messages over TLS - Agent Proxy now delivers large messages from a Client Workload when it connects to the Server Workload over TLS. This applies to MySQL, PostgreSQL, Amazon Redshift, Oracle Database, and Redis Server Workloads.
Credentials without a value - Agent Proxy and Aembit CLI no longer cache a credential that Aembit Cloud returns without a value, so the next request retrieves the credential again.
AWS Lambda packages - AWS Lambda Extension and AWS Lambda Layer bundle Agent Proxy 1.35.6254.

Tags:

Agent Controller 1.35.3776 release

October 29, 2026

Aembit has released Agent Controller version 1.35.3776 for Linux and Windows. For the latest available versions, see the Edge Components Supported Versions page.

AWS Metadata Service attestation behind an HTTP proxy - Agent Controller now bypasses an HTTP proxy when it calls the AWS instance metadata service for AWS Metadata Service Trust Provider attestation. It already bypassed the proxy for the Azure instance metadata service.
Agent Controller ID in authentication errors - When Agent Controller fails to authenticate with the Agent Controller ID you configured, the error now names that ID. The error asks you to confirm that the ID is valid and active in your Aembit Tenant.

Security updates also shipped in this build. See Agent Controller 1.35.3776 security updates.

Tags:

MCP Identity Gateway 1.35.6263 release

October 28, 2026

Aembit has released MCP Identity Gateway version 1.35.6263, which reports its version in its protected resource metadata and returns MCP server errors more reliably.

For the latest available versions of these components, see the Edge Components Supported Versions page.

Key Updates:

Version in protected resource metadata - The protected resource metadata document includes an aembit_gateway_version field, which you can read without an access token. See Check the MCP Identity Gateway version.
Credential available after authorization - After a user authorizes an MCP User-Based Access Token Credential Provider, MCP Identity Gateway uses the new credential on the user’s next request. Earlier versions returned errors for those requests until the cached credential expired.
MCP server errors with MCP Tool Access Control - If an MCP server returns an error while MCP Tool Access Control filters its tool list, the MCP client receives that error.
Header parameters across specification revisions - Some MCP servers on the 2026-07-28 MCP specification take a tool argument as a request header. MCP Identity Gateway sends that header for MCP clients on earlier revisions.
Credential injection failures in workload events - MCP Identity Gateway sometimes cannot add a credential to a request as a header or query parameter. The workload event then records the credential injection as failed.

A security update also shipped in this build.

Tags:

Access Authorization Events now record MCP client registrations

October 16, 2026

Access Authorization Events now include the access.registration event type. It records each Dynamic Client Registration (DCR) request that an MCP client sends to the MCP Authorization Server.

A successful registration has severity Info and lists the client ID, client name, redirect URIs, grant types, and response types that the MCP client registered.
A failed registration has severity Error and carries a reason and the attribute that failed, so you can see why an MCP client couldn’t register. When the request supplied a value for that attribute, the event also carries that value.

See Access registration events.

Tags:

Edge SDKs support the same Trust Providers in TypeScript and Python

October 16, 2026

The Edge SDKs for TypeScript and Python now attest with the same nine Trust Providers, so the language you pick no longer limits which Trust Providers your workload can use. For the full list, see Edge SDK Trust Providers.

What’s new:

Python Trust Providers: The Python SDK adds AWS Metadata Service, Azure Instance Metadata Service, GCP Identity Token, Kubernetes Service Account, and OIDC ID Token.
TypeScript Trust Providers: The TypeScript SDK adds GitLab, Kubernetes Service Account, and Terraform Cloud.
Python package on PyPI: Install the Python SDK with pip install aembit-edge-sdk. It requires Python 3.10 or later. See the Edge SDK quickstart.
Integration guides: New guides cover Azure Functions, Azure virtual machines, GitHub Actions, GitLab CI/CD, Kubernetes, and Terraform Cloud. Every integration guide now shows both languages.
Logging reference: Edge SDK logging and network activity lists the events the SDKs log, how to send them to your logger, and which hosts the SDKs contact.

Minimum version required:

Edge SDK for TypeScript 1.34.1
Edge SDK for Python 1.35.0

Tags:

Improved MCP Identity Gateway token, credential, and error handling

October 14, 2026

MCP Identity Gateway version 1.35.6086 accepts more access token audiences and sends credentials in named headers. It also reports more detail when an MCP server or a CrowdStrike AIDR inspection fails.

For the latest available versions of these components, see the Edge Components Supported Versions page.

Access token audience: MCP Identity Gateway accepts an access token whose audience is its /mcp endpoint URL with a trailing slash. See Token and credential details.
Credentials in a named header: When a Server Workload uses the Header authentication scheme, MCP Identity Gateway sends the credential to the MCP server in the header you name. MCP servers that take an API key in a custom header now receive it. See Authentication sent to the MCP server.
Longer list timeouts: The default tools_list, resources_list, and prompts_list timeouts are 5 seconds, up from 3 seconds. See AEMBIT_MCP_GATEWAY_TIMEOUT.
CrowdStrike AIDR timeouts in workload events: When a CrowdStrike AIDR inspection request times out, the workload event’s error message says so and gives the timeout. See Fail-open and fail-closed behavior.
MCP server connection errors: When MCP Identity Gateway can’t connect to the MCP server for a request such as tools/call, the MCP client gets error -32603. The error message names the failure, such as failed to connect to upstream MCP server. When the MCP server answered with an HTTP status, the error’s data carries it in upstreamHttpStatus, which replaces the status field that earlier versions sent. Update any client code that reads status.
Workload events for each MCP server: For tools/list, resources/list, and prompts/list, MCP Identity Gateway now emits a request event for each MCP server it fans the request out to. This includes a server it then skips because that server doesn’t support the method. These request events, and the event for each MCP server that fails, now name the Server Workload. A failure event also records the MCP server’s host and HTTP status when known. Review retention and alerting thresholds for the added request events. See Requests that fan out to multiple servers.

This build also adds change notifications and tool output validation and a security update.

Tags:

Access Policy builder search and Credential Provider value checks

October 14, 2026

The Select Existing tab in the Access Policy builder now searches and pages through all the entities you can access. Lists of more than 100 Client Workloads, Server Workloads, Trust Providers, Credential Providers, or Access Conditions no longer hide entries past the first page.

Credential Provider fields that take a Literal or Dynamic value now check the value against its type. Aembit rejects a save, including one through the API or Terraform, when a Literal value contains a ${...} expression or a Dynamic value contains no valid ${...} expression. In the Aembit Tenant UI, entering a ${...} expression in a field switches it to Dynamic. See Dynamic claims.

Tags:

MCP Server Workloads support more authentication methods

October 14, 2026

MCP Server Workloads can now use any authentication method that HTTP Server Workloads offer, such as API Key or HTTP Authentication with the Basic scheme. They can also define Static HTTP Headers. Selecting MCP still sets HTTP Authentication with the Bearer scheme by default, and you can change both. See Set up the MCP Authorization Server.

Tags:

Improved MCP Identity Gateway token validation and error reporting

October 7, 2026

MCP Identity Gateway version 1.34.6034 validates more access tokens and reports conflicting tool and prompt names. It also changes which timeout names take effect and what its request duration metric measures.

For the latest available versions of these components, see the Edge Components Supported Versions page.

ES256-signed access tokens: MCP Identity Gateway validates access tokens signed with ES256 as well as RS256. See Set up the MCP Identity Gateway.
Access token audience: MCP Identity Gateway accepts an access token whose audience is its /mcp endpoint URL, or its own URL with or without a trailing slash.
Tool and prompt name conflicts: Two Server Workloads assigned to the same MCP client can produce the same name prefix. MCP Identity Gateway then leaves both Server Workloads’ tools and prompts out of the client’s lists and logs the conflict. Rename one of the Server Workloads to fix it. See Tool and prompt names.
Timeout names with no effect: The initialize, notifications_initialized, proactive_tools_list, reinit_initialize, reinit_notifications_initialized, and reinit_tools_list timeout names no longer have an effect. MCP Identity Gateway still accepts them, so the service starts. If you set one of them, set upstream_call_timeout or the matching list timeout instead. See AEMBIT_MCP_GATEWAY_TIMEOUT.
Request duration excludes MCP server time: aembit_mcp_gateway_mcp_request_duration_seconds measures only the time MCP Identity Gateway spends processing a request, and excludes time spent waiting on MCP servers. Expect lower values, and review alerts and dashboards built on this metric. See Prometheus metrics.

This build also adds support for the 2026-07-28 MCP specification.

Tags:

Edge components release with Ubuntu 26.04 support

October 5, 2026

Aembit has released new versions of the following components and packages:

Agent Proxy 1.34.6014
Aembit CLI 1.34.6014
AWS Lambda Extension 1.34.185
Helm Chart 1.34.571
AWS ECS Terraform 1.34.4

For the latest available versions of these components, see the Edge Components Supported Versions page.

Key Updates:

Agent Proxy installs on Ubuntu 26.04 LTS: The Linux installer now completes on Ubuntu 26.04 LTS hosts. See Supported versions.
Private Network Access credential retrieval: Agent Proxy retrieves and injects credentials for Access Policies whose Credential Provider uses Private Network Access. Agent Proxy 1.34.5755 could fail credential retrieval for these Access Policies.

A dependency security fix also shipped in this build. See Edge components dependency security updates.

Tags:

Automatic user creation reads user names from more claims

September 23, 2026

When Aembit creates a user through single sign-on, it now reads the user’s first and last names from standard OpenID Connect (OIDC) profile claims, including given_name and family_name. If a first or last name claim is missing, Aembit takes that name from the name claim.

For the full list of claims, see User name claims.

Tags:

Dynamic claims now support SAML assertions

September 23, 2026

Dynamic claims can now read values from a SAML 2.0 response, so a Credential Provider can issue a credential bound to each SAML user’s own identity.

Aembit receives SAML responses when users sign in through the MCP Authorization Server or the MCP Identity Gateway. A SAMLv2 Response Trust Provider validates each response, and three expressions read values from its assertion:

${saml.response.subject.nameId} returns the Subject NameID that identifies the user.
${saml.response.issuer} returns the identity provider that issued the assertion.
${saml.response.attributes['<name>']} returns a named attribute, such as a user’s groups.

If a SAML expression can’t resolve to a value, Aembit denies the request and issues no credential. The Credential Provider form in the Aembit Tenant UI shows the SAML syntax with examples. See SAML assertion claims.

Tags:

Kubernetes Service Account Trust Provider now supports multiple OIDC endpoints

September 23, 2026

A Kubernetes Service Account Trust Provider now accepts more than one OpenID Connect (OIDC) endpoint. One Trust Provider can then attest a Client Workload that runs active-active across two or more clusters.

Each cluster signs its Service Account tokens with its own key. Add one OIDC Endpoint for each cluster’s issuer URL with Add an Endpoint, and the Trust Provider validates a token signed by any of them. See Attest one workload across multiple clusters.

Tags:

Agent Controller 1.34.3725 release

September 17, 2026

Aembit has released Agent Controller version 1.34.3725 for Linux and Windows. For the latest available versions, see the Edge Components Supported Versions page.

Kerberos attestation on AWS EC2: An Agent Controller running on an AWS EC2 instance now completes Kerberos Trust Provider attestation requests from Agent Proxy. Agent Controller 1.32.3541 on EC2 answered those requests with an HTTP 500 error. Upgrade any Agent Controller that runs on EC2 and serves Kerberos attestation to 1.34.3725 or later.
Windows certificate chain validation: On Windows, Agent Controller now installs the intermediate CA certificates from its TLS certificate chain into the LocalMachine certificate store, so Windows TLS clients can validate the full chain.
Windows service logon account on reinstall: When you uninstall Agent Controller on Windows and reinstall it with a different SERVICE_LOGON_ACCOUNT, the installer now grants the new account access to the existing log file before the service starts, so logging continues. Changing the logon account of an installed service is still unsupported.
TLS certificate status reporting: Agent Controller reports its TLS certificate status to Aembit Cloud consistently during certificate renewal.
Container base image: The container image uses updated base image digests so it starts on newer container runtimes.

Tags:

Aembit Cloud configuration updates

September 16, 2026

Aembit Cloud corrects configuration workflows across Content Security, Client Workloads, Trust Providers, and authorization event reporting.

Key Updates:

Content Security tool lists: Switching between Allow and Block in a Content Security Provider keeps the tool list you configured, and Remove Tools clears the whole list in a separate step that asks you to confirm.
Redirect URI fields: A Redirect URI field on a Client Workload accepts a pasted value in every position, inserts a long pasted value rather than overwriting the text around it, and shows one validation message at a time. Copying the full contents of a field leaves the browser responsive.
Trust Provider secrets in custom Resource Sets: Terraform reads the state of a Trust Provider secret when that Trust Provider belongs to a custom Resource Set.
Authorization event timespan filters: The date filters on Access Authorization Events offer a maximum timespan of 24 hours, the window over which the Aembit Tenant UI makes authorization events available.

Tags:

Developer Guide combines the API, CLI, and SDK documentation

August 27, 2026

The Developer Guide is now the single home for every way you integrate with Aembit from code, commands, or infrastructure. It replaces the separate API Guide and CLI Guide, which each covered one surface and left you to work out which one fit your workload. The new Edge SDK section lands inside it rather than beside it.

The guide opens by separating the two decisions an integration involves. First, choose how your workload gets a credential at runtime, through Agent Proxy, the Edge SDK, the Aembit CLI, or the Edge API. Second, choose how you manage the Aembit configuration behind that path, in the Aembit Tenant UI, through the Cloud API, or as Terraform code.

What’s new:

One guide for every developer surface: Aembit SDKs, Aembit APIs, Aembit CLI, Agent Proxy, and the local development and testing pages all sit under /dev-guide/.
A comparison of every credential path: The overview compares Agent Proxy, the Edge SDK, the Aembit CLI, and the Edge API side by side, so you can pick one before you read its section.
Shared local development and testing pages: One page covers local development and one covers testing and debugging across every integration path.

Every URL under the old /api-guide/ and /cli-guide/ paths redirects to its new location, so existing bookmarks and links keep working.

Tags:

Edge components release with Agent Proxy fixes and expanded workload events

August 27, 2026

Aembit has released new versions of the following components and packages:

Agent Proxy 1.34.5755
AWS Lambda Extension 1.34.175
Agent Injector 1.34.433
Sidecar Init 1.34.138
Helm Chart 1.34.566
AWS ECS Terraform 1.34.1
Aembit CLI 1.34.5772

For the latest available versions of these components, see the Edge Components Supported Versions page.

Key Updates:

Workload events carry the authorization chain: Agent Proxy events now include the authorizationChain field, an ordered list of the context IDs of the authorization events behind the request, so you can trace an event back to the directive and credential retrievals that authorized it.
Aembit-generated responses keep their outcome fields: When Aembit answers a request in place of the Server Workload, the response event now reports the generated response’s severity, outcome.result, and outcome.reason. Earlier versions cleared those fields between the request and the response, so the event recorded an incomplete outcome.
Windows installer honors the gRPC keep-alive properties: The MSI now applies AEMBIT_TENANT_GRPC_PING_INTERVAL_SECS and AEMBIT_TENANT_GRPC_PING_TIMEOUT_SECS when you pass them as install-time properties. See Configuring gRPC keep-alives.
Linux installer validates Agent Proxy arguments: The Linux installer script now checks Agent Proxy arguments before it installs, so an invalid value in a numeric environment variable such as AEMBIT_HTTP_IDLE_TIMEOUT_SECS is reported at install time.
Container image updates: Agent Injector and Sidecar Init move to a newer Debian base image, and AWS Lambda Extension updates its Go version.

Dependency security fixes also shipped in this build. See Edge components dependency security updates.

Tags:

MCP Identity Gateway 1.34.5733 release

August 18, 2026

Aembit has released MCP Identity Gateway version 1.34.5733.

For the latest available versions of these components, see the Edge Components Supported Versions page.

Key Updates:

Higher fanout timeout defaults: The Gateway now waits longer for your assigned MCP servers on most of the MCP methods it fans out, which gives a server that’s still starting up, or one answering from a cold cache, room to respond. A self-hosted Gateway can override any of these timeouts as a last resort; see MCP Identity Gateway raises fanout timeout defaults.
Nine new Prometheus metrics: The Gateway’s metrics endpoint reports on upstream fanout behavior, authentication failures, JWKS refreshes, session cleanup, and readiness probe stability.
Every Gateway metric documented: The metrics reference now lists all 20 MCP-specific metrics the Gateway exposes, with the type and labels for each and the values each label takes. See Prometheus metrics.

Tags:

MCP Identity Gateway raises fanout timeout defaults

August 18, 2026

MCP Identity Gateway 1.34.5733 raises how long the Gateway waits for your assigned MCP servers when it fans a request out to them. The earlier defaults were short enough that a server still starting up, or one answering from a cold cache, could run past them.

Timeout	1.33.5654	1.34.5733
`initialize`	`3s`	`10s`
`notifications_initialized`	`500ms`	`1s`
`tools_list`	`1s`	`3s`
`proactive_tools_list`	`3s`	`5s`
`resources_list`	`1s`	`3s`
`reinit_initialize`	`10s`	`10s`
`reinit_notifications_initialized`	`500ms`	`1s`
`reinit_tools_list`	`1s`	`5s`

reinit_initialize is the one timeout this build leaves unchanged.

The new defaults require no configuration and apply to both deployment models as soon as you upgrade. They’re high enough that an AI client typically reaches its own timeout before the Gateway reaches one of these, so most deployments never need to change them.

A self-hosted Gateway can override any of these timeouts as a last resort, using the AEMBIT_MCP_GATEWAY_TIMEOUT environment variable. The installer doesn’t forward this variable to the running service, so setting it takes a systemd drop-in. For the accepted names, the value format, and the drop-in, see MCP Identity Gateway environment variables. Aembit sets these values for you on the Aembit-managed service.

These updates shipped in the same build as the MCP Identity Gateway 1.34.5733 release.

Tags:

Aembit Access Token lifetime has a 300 second minimum

August 11, 2026

The Lifetime field on an Aembit Access Token Credential Provider now accepts a minimum of 300 seconds (5 minutes). The Admin UI, the Aembit API, and the Aembit Terraform provider all enforce the same minimum, so any shorter value fails validation wherever you set it.

The default lifetime stays at 900 seconds (15 minutes).

See Aembit Access Token.

Tags: