Agent Controller 1.32.3541 includes security hardening for the container image that reduces its attack surface and strengthens supply chain integrity. The image now ships with a bundled software bill of materials for greater transparency into its contents.
Aembit now offers an OpenAI Workload Identity Federation (WIF) Credential Provider. Your workloads can call the OpenAI API with short-lived tokens that Aembit obtains on their behalf instead of long-lived API keys.
Aembit acts as a trusted OIDC issuer. You register Aembit as a Workload Identity Provider in OpenAI. Then, whenever an Access Policy grants a workload access, Aembit exchanges its issued assertion for a short-lived OpenAI access token.
What’s new:
For setup instructions, see Configure an OpenAI WIF Credential Provider.
Aembit can now identify MCP client workloads with a Client ID Metadata Document (CIMD).
A CIMD is a JSON document the client hosts at a public HTTPS URL, and the URL itself serves as the client’s identity.
When the client presents the URL-formatted client_id, Aembit fetches the document and validates the client’s
metadata, so the client can authenticate without Dynamic Client Registration.
CIMD has reached general availability, and Aembit enables it by default. To identify a Client Workload by its CIMD URL, see CIMD Client ID.
MCP Identity Gateway now binds each session ID to the authenticated user, closing a privilege-escalation gap where one user’s session could carry over to another identity.
This change requires no configuration. It ships in MCP Identity Gateway 1.32.5098, alongside the workload event correlation and platform fixes in this build; see the event correlation and platform fixes entry.
This update brings event correlation to MCP Identity Gateway workload events, along with fixes across Credential Provider, Access Policy, and Client Workload workflows.
This update includes:
For the latest available versions of these components, see the Edge Components Supported Versions page.
Key Updates:
Session IDs are now bound to the authenticated user in this build, closing a privilege-escalation gap; see the Security entry. Client ID Metadata Document (CIMD) identification also reached general availability in this update; see the announcement.
You can now delete a custom Resource Set: Resource Sets are organizational containers that group Access Policy components together, enabling you to manage configurations across different environments, regions, or use cases.Learn more when you no longer need it. Deletion is a cascading, all-or-nothing operation: Aembit removes the Resource Set and every entity it contains in a single action that either completes fully or rolls back.
What’s new:
aembit_resource_set resource.
Destroying an aembit_resource_set performs the identical cascading delete, and the resource_set_id argument
assigns or filters entities by Resource Set.For the full workflow and its effects, see Delete a Resource Set. For managing Resource Sets as code, see Scaling Aembit with Terraform.
Aembit now offers a Claude Workload Identity Federation (WIF) Credential Provider. Your workloads can call the Claude API with short-lived tokens that Aembit obtains on their behalf instead of long-lived API keys.
Aembit acts as a trusted OIDC issuer. You register Aembit as a federation issuer in Claude Console. Then, whenever an Access Policy grants a workload access, Aembit exchanges its issued assertion for a short-lived Claude access token.
What’s new:
For setup instructions, see Configure a Claude WIF Credential Provider.
Aembit has released new versions of the following components and packages:
For the latest available versions of these components, see the Edge Components Supported Versions page.
Key Updates:
aembit credentials get command now supports
the AWS Metadata Service, AWS Role, and Kubernetes Service Account Trust Providers.
Aembit CLI gathers attestation data from the local environment—instance metadata, an STS GetCallerIdentity
request, or the projected service account token—so an externally supplied
--id-token isn’t needed for these Trust Providers.
The --deployment-model option now accepts vm,
kubernetes, ecs_fargate, and lambda_container.
The AWS Role Trust Provider requires this option.Aembit Secrets Operator 1.32.322 is now available.
Secrets Operator now retrieves any credential type your Access Policy
issues—not just HashiCorp Vault tokens.
A new credentialType field on the AembitSecretRefreshSchedule resource selects which Credential Provider type Aembit
uses, and the managed Kubernetes Secret mirrors the Aembit Edge API credentials response for that provider.
credentialType field: Choose OAuthToken (the default), ApiKey, UsernamePassword, AwsStsFederation,
or GoogleWorkloadIdentityFederation.
Each type writes its own Secret data keys—for example, UsernamePassword produces username and password, and
AwsStsFederation produces awsAccessKeyId, awsSecretAccessKey, and awsSessionToken.
See Credential types and Secret data keys.credentialType keep writing a single token key, so existing
HashiCorp Vault and cert-manager configurations need no change.credentialType doesn’t match the configured Credential Provider, the schedule
reports Aembit Edge API returned a credentials response with no populated fields instead of writing a blank Secret.A security update for Agent Proxy resolves a vulnerability in a bundled DNS library.
This fix shipped in the same build as the Edge components release with reliability, CLI, and MCP enhancements, across the Agent Proxy container, virtual machine package, and AWS Lambda deployments.
Aembit has released new versions of the following components and packages:
For the latest available versions of these components, see the Edge Components Supported Versions page.
Key Updates:
aembit credentials get command now accepts
--client-tls-private-key to retrieve a
SPIFFE-compliant X.509-SVID certificate from the existing
X.509-SVID Credential Provider. You supply
a PEM-encoded private key; Aembit CLI generates the certificate signing request locally and returns the signed chain
in CLIENT_CERT_CHAIN,
and the private key never leaves the local machine.AEMBIT_TENANT_GRPC_PING_INTERVAL_SECS and
AEMBIT_TENANT_GRPC_PING_TIMEOUT_SECS,
let Agent Proxy send keep-alives on its connection to your Tenant so it detects a dead connection and reconnects
faster. They’re off by default and useful for networks, such as a Secure Web Gateway, that stall idle connections.AGENT_TRUST_PATH again lets you supply a
custom CA certificate for the Agent Proxy’s connection to the Aembit Cloud, which is useful when an inspecting proxy
terminates TLS on outbound traffic.AEMBIT_HTTP_IDLE_TIMEOUT_SECS,
letting you tune the idle timeout for HTTP/1.1 connections handled by the Agent Proxy.Aembit has released MCP Identity Gateway version 1.32.5006.
For the latest available versions of these components, see the Edge Components Supported Versions page.
Key Updates:
ping method, responding to client connection-health checks
per the MCP specification.Aembit CLI now retrieves SPIFFE-compliant X.509-SVID certificates directly from the X.509-SVID Credential Provider.
Aembit has released new versions of the following components and packages:
For the latest available versions of these components, see the Edge Components Supported Versions page.
Key Updates:
aembit credentials get command now accepts
--client-tls-private-key to retrieve a
SPIFFE-compliant X.509-SVID certificate from the existing
X.509-SVID Credential Provider.
You supply a PEM-encoded private key; Aembit CLI generates the CSR locally, submits it through the credential
retrieval flow, and returns the signed certificate chain in CLIENT_CERT_CHAIN.
The private key never leaves the local machine.Introducing end-to-end mutual TLS (mTLS) between Client Workloads and Server Workloads using SPIFFE-compliant X.509-SVID certificates.
Aembit has released new versions of the following components and packages:
For the latest available versions of these components, see the Edge Components Supported Versions page.
Key Updates:
x509 Certificate scheme, lets Server Workloads validate the client certificate that Agent Proxy presents during the
mTLS handshake.Agent Proxy can now establish outbound mTLS connections to Server Workloads using SPIFFE-compliant X.509-SVID certificates, enabling certificate-based workload-to-workload authentication without application code changes.
What’s new:
x509 Certificate scheme) lets the Server Workload side validate the X.509-SVID certificate that Agent
Proxy presents during the handshake.For the end-to-end workflow and procedure, see Enable mTLS on a Server Workload. For the authentication-method catalog, see Authentication methods and schemes.
Aembit is introducing a new X.509-SVID Credential Provider type that issues SPIFFE-compliant X.509 certificates to Client Workloads, signed by an Aembit Standalone CA.
What’s new:
id-kp-clientAuth for outbound mTLS, or add
id-kp-serverAuth to use the same certificate as a server credential.For setup instructions, see Create an X.509-SVID Credential Provider. For concepts and the end-to-end issuance flow, see About the X.509-SVID Credential Provider.
Aembit has expanded the event coverage and reporting surfaces for troubleshooting MCP and AI IAM failures:
access.discovery event type: Access Authorization Events now include an access.discovery event that
lists the Client Workloads and Server Workloads Aembit Cloud considered during evaluation. Use it to diagnose
requests that match no workload or policy, or that match multiple. See
Access Discovery events.userId field at
application.mcp.userId for flows that involve a human identity, such as MCP Authorization Server flows. The
Workload Events view exposes a matching User (MCP App Protocol only) filter for per-user investigations and
SIEM scoping.Error severity rather than warning, so SIEM alerts that watch for Error events catch real authorization
failures reliably.access.credential event’s reason now identifies which token
expired and at which step, making it easier to decide between re-authentication, credential refresh, or
Credential Provider reconfiguration.For an end-to-end investigation flow that uses these reporting surfaces together, see Troubleshoot MCP and AI IAM access.
Aembit has released MCP Identity Gateway version 1.31.4955.
For the latest available versions of these components, see the Edge Components Supported Versions page.
Key Updates:
Aembit Secrets Operator 1.31.314 is now available.
This release graduates the Secrets Operator CRDs from v1beta1 to v1.
Use apiVersion: aembit.io/v1 in your manifests—see the
Configuration Reference for the updated specs.
Aembit Secrets Operator 1.31.298 is now available.
Secrets Operator is a Kubernetes operator that authenticates to the Aembit platform and synchronizes credentials into Kubernetes Secrets. Applications consume managed secrets the same way they consume any other Kubernetes Secret.
Key capabilities in this release:
refreshInterval, ensuring applications always have a valid credential.Aembit has released MCP Identity Gateway version 1.31.
Key Updates:
userId field now appears on mcp.request and mcp.response
workload events when the MCP client is
identified, making it easier to attribute MCP activity to authenticated users in audit reports.DELETE request to the /mcp endpoint, per
MCP specification section 2.5.5.
See Session management for the request
contract.Custom environment variables on Agent Proxy and Aembit CLI can now feed into OIDC and JWT-SVID dynamic claims, gated by an explicit allowlist.
What’s new:
AEMBIT_ENV_VAR_ALLOWLIST: A new environment variable that defines which custom variables
Agent Proxy and Aembit CLI may capture for use in dynamic claims. By default, Agent Proxy and
Aembit CLI capture no custom variables.K8S_POD_NAME, K8S_NAMESPACE, and
KUBERNETES_PROVIDER_ID are now usable in dynamic claims regardless of the allowlist.For setup instructions, see Configure custom environment variables for Agent Proxy. For the dynamic claims expression syntax, see OIDC and JWT-SVID dynamic claims.