mTLS
mutual TLS · mutual-TLS · mutually-authenticated TLS
By Boston Identity · Explained · 6 min read
The short answer
Mutual TLS is a connection where the client, like the server, shows a certificate and proves it holds the private key. In OAuth, it can replace a client secret and tie an access token to the client.
- What it is
- A protocol
- Defined by
- IETF, RFC 8705 (its use in OAuth)
- Who it's for
- Teams securing service and agent access to APIs
- In our briefings
- 1060by month, last 12
What is mTLS?
Ordinary TLS (Transport Layer Security, the encryption behind HTTPS) proves the server's identity to the client. In mutual TLS, the client also sends its own X.509 certificate during the handshake and proves it holds the matching private key.§1.2
RFC 8705, an IETF (Internet Engineering Task Force) standard from February 2020, brings this into OAuth, the framework that lets an application get an access token and use it at an API.§1 A client can authenticate to the authorization server with its certificate in place of a shared secret, which the RFC says gives better security.§1 The authorization server can also bind the access token to that certificate. Anyone who holds an ordinary bearer token can use it, while a bound token works only for the party holding the certificate's private key, so a stolen or replayed token is useless.§1
The RFC treats the two uses as separate: they work well together, and a deployment can run either one alone.§1 A public client, one with no credentials of its own, can still get bound tokens by making a self-signed certificate.§4
Not the same as the HTTPS a browser uses every day, where only the server shows a certificate. Mutual TLS also does not bind tokens by itself: certificate-bound tokens are a separate feature that an authorization server advertises when it supports them.§3.3
How does mTLS work?
Three parties take part: the client (an application or agent), the authorization server that issues tokens, and the resource server, which is the API the client wants to reach. The client talks to both servers over mutual TLS.
Figure steps
- The server asks for the client's certificate
- The client names itself at the token endpoint
- The authorization server checks the certificate
- The authorization server binds the token to the certificate
- The client reaches the API with the same certificate
- The API compares the certificate with the token
The client proves its certificate at the token endpoint, gets a token bound to it, and must show the same certificate at the API.
Drawn from RFC 8705, sections 2 and 3
Swipe for the full figure →
The server asks for the client's certificate
During the TLS handshake, the server requests a certificate; a client does not send one unasked.§5 The client sends its X.509 certificate and a signed CertificateVerify message, which proves it holds the private key. The server checks that message and the handshake's Finished message.§1.2
The client names itself at the token endpoint
Over that connection, the client asks the authorization server for a token and must include its client_id, the name it is registered under.§2 The server looks up that client's settings and checks the certificate from the handshake against them. A missing or wrong certificate gets the standard OAuth error invalid_client.§2
The authorization server checks the certificate
Under the PKI (public key infrastructure) method, the server validates the certificate chain and matches one subject name registered for that client, such as a distinguished name or a DNS name.§2.1 Under the self-signed method, the client registers its certificates in advance. The server skips chain validation and checks that the certificate matches one of them.§2.2
The authorization server binds the token to the certificate
When the token is a JSON Web Token (JWT), the server should place a SHA-256 hash of the certificate, its thumbprint, in the token's cnf (confirmation) claim as x5t#S256.§3.1 When the API checks tokens by introspection, a lookup at the authorization server, the same hash comes back in the response.§3.2
The API compares the certificate with the token
The resource server must take the client certificate from its TLS layer and check that it matches the one tied to the token. If they differ, it must reject the request with HTTP 401 and the error invalid_token.§3 The API does not need to validate the certificate's chain, because here mutual TLS only proves possession of the key.§6.2
Why does mTLS matter now?
Revision -15 of OAuth 2.1 recommends asymmetric client authentication and names mutual TLS and signed JWTs as examples.1 For public clients, the draft requires the authorization server to catch a reused refresh token. Binding the token to the client instance with DPoP (Demonstrating Proof of Possession) or mutual TLS is one of the two ways it gives.2
Agent security guidance asks for certificates as well. Anthropic's zero trust guide for agents adds X.509 certificates with rotation and revocation, and then mutual TLS, at its higher tiers.3 OWASP's top 10 for agentic applications names mutual TLS certificates as one example of the short-lived, narrowly scoped credentials it wants for each task.4 The agent protocols themselves leave it optional. An Agent2Agent (A2A) 1.0 agent card may declare mutual TLS among five methods, and none is required.5 The July 2026 Model Context Protocol (MCP) specification does not require sender-bound tokens at all.6
On the workload side, an OAuth working-group draft lets a workload present its SPIFFE certificate over mutual TLS in place of a stored secret.7 The IETF's workload identity group also has a mutual TLS profile, but it leaves trust anchor distribution out and gives revocation a single paragraph with no numbers.8
Where does it fit?
| Compared with | How mTLS differs |
|---|---|
| DPoP | Both tie an OAuth token to a key the client holds, and OAuth 2.1 offers either one to stop refresh-token replay.2 Mutual TLS proves the key in the TLS connection, so the proof ends at any proxy or gateway that ends the connection.9 |
| SPIFFE | SPIFFE gives a workload an identity and credentials that carry it, one of which is a certificate. Mutual TLS is one way to present that certificate, and an OAuth draft uses it so a workload can authenticate without a stored secret.7 |
| OAuth | OAuth is the framework for issuing and using access tokens. Mutual TLS plugs into it twice: as a way for a client to authenticate without a shared secret, and as a way to make its tokens useless to a thief.§1 |
What goes wrong?
- A proxy ends the proof. The RFC lets servers end TLS at a load balancer or proxy, but how the certificate details then reach the application server is out of its scope.§6.5 Mutual TLS proves the identity only as far as the TLS connection reaches,10 and a draft on agent authentication says it breaks at every proxy, gateway and service mesh that ends the connection.9
- Under the PKI method, an attacker could present a certificate with the same subject name, issued by another certificate authority (CA) the server trusts. The server should trust only a few CAs whose issuing rules meet its needs.§7.4
- X.509 validation is complex, and mistakes in it have caused security holes before. Implementers should use a well-tested library and should not write their own checks.§7.5
- Whether and how to check if a certificate was revoked is left to the authorization server.§2.1
- A new certificate invalidates the tokens bound to the old one, so the client has to get new tokens, usually with a refresh token.§6.3
- Before TLS 1.3, the client certificate travels unencrypted, and third parties can use it to track a client.§8
- When a server asks for a certificate, a browser may show the user an intrusive certificate picker. The RFC lets servers offer separate mutual TLS endpoints to keep that away from ordinary clients.§5
What should a security leader ask?
- 01
Where does TLS end between our clients and our APIs, and what checks the client certificate after that point?
- 02
Do our access tokens carry a certificate thumbprint, and does every API compare it with the certificate on the connection?
- 03
Which certificate authorities does our authorization server trust for client certificates, and who could get one with a subject name that matches one of our clients?
- 04
What happens to an agent's tokens when its certificate rotates, and how fast can we revoke a stolen certificate?
- 05
Which of our agent connections, over MCP or A2A, let a client skip mutual TLS or token binding?
Sources
- S1
OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensIETF · RFC 8705, Standards Track, February 2020
›Evidence: 10 claims from 8 briefings
- 1BI-FIND-2026-1112 · OAuth 2.1's March draft builds in the security best practice, but 2.1-only clients can fail with older serversOAuth 2.1 specifies how a client authenticates but leaves validating who the client is to the authorization server. In the editors' words, "Whether and how an Authorization Server validates the identity of a client or the party providing/operating this client is out of scope of this specification." Section 2.4 gives the authentication side with examples: asymmetric methods are RECOMMENDED, such as mutual TLS or signed JWTs (private_key_jwt), and where a client cannot authenticate the server SHOULD use other means, for example requiring the redirect URI to be registered or asking the resource owner to confirm identity. Servers SHOULD weigh their confidence in a client's identity before allowing more sensitive access, such as the client credentials grant, and the attestation-based client authentication draft comes up only in the native-apps section, as a way to raise assurance of a mobile app's identity.
- 2BI-FIND-2026-1109 · OAuth 2.1's March draft builds in the security best practice, but 2.1-only clients can fail with older serversRevision -15 of OAuth 2.1 turns the advice in OAuth 2.0's security best current practice (RFC 9700) into the base protocol. The authorization code grant now carries PKCE: clients are REQUIRED to send a code challenge and authorization servers MUST enforce it, unless the client is confidential and the server has reasonable assurance that it implements the OpenID Connect nonce properly. Redirect URIs are registered in full and must match exactly, except for the port on loopback redirects. The implicit and password grants are left out, clients MUST NOT send access tokens in a URI query parameter, and for public clients the authorization server MUST catch refresh-token replay, either by binding the token to the client instance (DPoP and mutual TLS are the examples given) or by rotating it on every refresh.
- 3BI-FIND-2026-0596 · Anthropic asks for per-agent identity; its guide leaves Claude Code sub-agent credentials unspecifiedAnthropic requires a cryptographic identifier for each agent instance at its Foundation tier. "Every agent instance needs a unique, cryptographically rooted identifier that persists across its actions", and "Unique identifiers alone are a labeling exercise". Service tokens should be measured in minutes, and static API keys and shared service-account passwords "are no longer a legitimate entry point, not even at Foundation". Higher tiers add X.509 certificates with rotation and revocation, mutual TLS, then hardware-backed identity with remote attestation, and access control climbs from deny-by-default roles to per-action authorization with immediate revocation. The standards named are OAuth 2.0, X.509, mTLS, FIDO2 and OpenTelemetry; SPIFFE, WIMSE and token exchange do not appear.
- 4BI-FIND-2025-0093 · OWASP's agent Top 10 blames identity systems built for people, and does not say how it chose or ranked its risksOWASP's identity entry, ASI03 Identity and Privilege Abuse, puts the root cause in "the architectural mismatch between user-centric identity systems and agentic design": without "a distinct, governed identity of its own, an agent operates in an attribution gap that makes enforcing true least privilege impossible." Its nine mitigations ask for per-agent identities, "short-lived, narrowly scoped tokens per task" such as mTLS certificates or scoped tokens, a policy check on every action, human approval for escalation, and OAuth tokens bound "to a signed intent that includes subject, audience, purpose, and session". It names no standard for any of them: token exchange, SPIFFE, OIDC, DPoP and the MCP authorization specification appear nowhere in the 57 pages.
- 5BI-FIND-2026-0760 · A2A 1.0 connects agents across companies and leaves out the person they act forA2A 1.0 authenticates the calling agent and stops there. An agent's card can declare API keys, HTTP authentication, OAuth 2.0, OpenID Connect or mutual TLS, none of them required, and credentials are fetched out of band and sent with every request. Nothing in the core protocol carries the person the work is done for or the agents a task passed through: 'Identity information is handled at the protocol layer, not within A2A semantics'. Authorization, including authorization by the user's identity, which the specification lists as an option, is left to each implementation, and extensions are the hook for adding more. There is no token exchange, no actor claim and no on-behalf-of field. An enterprise that lets a partner's agent call its own over A2A has to bring the user's identity and the delegation record in its own tokens.
- 6BI-FIND-2025-0015 · An early MCP security checklist was never tested, and the protocol has since adopted only part of itMeasured against this 2025 checklist, the Model Context Protocol's own rules now cover one part of the identity advice and leave the rest to whoever deploys it. The paper asked for tokens restricted to one audience, short-lived and narrowly scoped, bound to the sender with DPoP or mutual TLS, issued just in time and per tool, with rich authorization requests for fine-grained grants. The July 2026 specification makes audience binding mandatory and forbids passing a token on. It does not require sender binding, per-tool grants or just-in-time issuance, and authorization itself remains optional. A team that reads the specification as a security baseline gets the first of those and none of the others.
- 7BI-FIND-2026-0316 · A draft lets a workload sign in to OAuth with its SPIFFE identity, not a secret; one preview supports part of itAn OAuth working-group draft lets a workload authenticate to an authorization server with the identity its platform issued, in place of a stored secret. It covers three forms of SPIFFE credential: a signed token presented under a new assertion type, a certificate presented over mutual TLS, and a key-bound workload token with a proof of possession. A server must advertise which it accepts and support at least one. This is the missing piece between workload identity and OAuth that speakers in this corpus have been calling duct tape, now on the standards track. One implementation is listed, Keycloak, in preview, for the first of the three forms.
- 8BI-FIND-2026-0517 · The IETF's workload mutual-TLS profile leaves the certificate, trust anchors and revocation to other documentsThe profile adds little on its own. Hostname validation under RFC 9525 stays exactly as it is when a client connects by DNS name; the workload identifier rides as an extra identity in a URI subject alternative name, placed and counted by reference to the WIMSE credentials draft; and authorization "MUST NOT" evaluate the identifier's path without its trust domain and trust anchor. Trust anchors are simply "configured for the trust domain", with no bundle distribution, and revocation and certificate lifetime get one SHOULD paragraph with no numbers, CRL or OCSP. AI agents are not mentioned.
- 9BI-FIND-2026-0180 · Six rival vendors wrote the agent-identity draft the IETF just adopted, and it invents nothingThe draft names the gateway problem our corpus keeps circling and puts the fix at a different layer. Mutual TLS gives an agent 'strong channel binding and cryptographic proof of control over the agent's private key', and it breaks at every proxy, gateway and service mesh that terminates the connection, which is where enterprises put their agent gateways. So authentication moves to the application layer: a Workload Proof Token, 'a signed JSON Web Token that binds an agent's authentication to a specific message context', or an HTTP message signature, either of which survives an intermediary at the cost of needing short lifetimes and replay defences. Uber already chose the application layer by putting token exchange in its SDK rather than trusting the mesh; Sierra's proxy is the intermediary this section is about. Whether a gateway can carry the chain remains open; what the draft settles is that the channel cannot.
- 10BI-FIND-2026-0518 · The IETF's workload mutual-TLS profile leaves the certificate, trust anchors and revocation to other documentsMutual TLS proves the identity only as far as the TLS connection reaches. Section 5 tells deployments whose traffic crosses a TLS-terminating proxy to add an application-layer WIMSE mechanism on top, without naming one; the working group's HTTP-signature profile is built around exactly that proxy, so we read that profile as the expected companion to this one.
›In our briefings
The claim each of the newest briefings on mTLS would have you leave with.
Revision -02 of Shankarlingam's draft says the delay before a disabled agent is refused is "a property of the receiver's configuration, not of the token alone", and that passing the receiver's checks does not show a disabled client is refused within the bound the receiver computes. Raising the maximum token age, DNS caching, caching of issuer metadata and keys, or the clock-skew allowance lengthens the time a disabled client is still accepted, while every signature, issuer, client, audience and DNS check keeps passing. Those checks, the draft says, "establish that a token is authentic; they do not establish that the client is still enabled." A receiver SHOULD recompute the bound before any change to those settings takes effect, and SHOULD test it directly, again after any change to those settings: obtain link tokens for a test client, disable it at a time not known to whoever observes the receiver, keep presenting tokens issued before the disable, and compare the last acceptance with the time the authorization server records the disable. The receiver meets its bound if that gap does not exceed the computed delay. It SHOULD also log the maximum age in effect with each verification result, and the security section says receivers SHOULD treat such changes as security relevant. The draft describes this test and reports no results from running it.
A disabled agent's old tokens still pass every check; a DNS draft now asks receivers to time how longBI-FIND-2026-2345
AAuth's premise is that an OAuth client or an API key has no identity of its own and that SPIFFE and WIMSE stop at one trust domain, so it gives each agent one: an identifier of the form aauth:local@domain issued by an Agent Provider and bound to the agent's own signing key by a short-lived agent token (the draft recommends Ed25519, which every party must support), so that 'every agent has its own cryptographic identity' and 'the first API call to a resource is the registration'. No credential in the protocol is a bearer credential; every request is signed, and a resource can challenge for more at any time. In its lightest mode the draft pitches this as a drop-in for API keys: 'this replaces API keys with cryptographic identity.' What an agent token attests about the software behind the key is left to companion specifications.
AAuth gives every agent its own key, then keeps the delegation chain out of the token on purposeBI-FIND-2026-0365
Asor's chain names its principal at every hop but cannot show that the principal still holds the grant. Every token's sub must carry the same value, the party "whose grant the chain acts under"; a required client_id names the agent acting at each hop, and step 3 denies a chain whose sub changes. A row added to Table 1 in -03, credited to Cliff Singletary, records the limit: nothing in a chain says whether the principal named in sub still holds the authority the root token granted. A principal who has left, lost the role or had the grant withdrawn leaves every unexpired, unrevoked chain verifying clean, because a status list revokes tokens and nothing in the chain revokes the principal. A deployment that must know checks standing when the root token is issued, which is also where the draft puts approval. Where the gap after minting is unacceptable, an online server in the call path checks again at use. Approval at the root has its own limit: verification shows that no hop exceeded the root, "never that the root was right".
Asor's agent-chain draft now says a chain keeps verifying after its principal leaves, until expiry or revocationBI-FIND-2026-1335
›Cited in 106 briefings
Every briefing that discusses this term, newest first.
- A disabled agent's old tokens still pass every check; a DNS draft now asks receivers to time how long
Draft · · IETF Datatracker · Sriram Shankarlingam, HexaEight · Oct 20, 2026
- AAuth gives every agent its own key, then keeps the delegation chain out of the token on purpose
Draft · · IETF Datatracker · Dick Hardt, Hellō · Sep 25, 2026
- Asor's agent-chain draft now says a chain keeps verifying after its principal leaves, until expiry or revocation
Draft · · IETF Datatracker · Rafael Asor · Oct 28, 2026
- Transaction Tokens carry who started a request through internal services and define no list of the hops in between
Draft · · IETF OAuth Working Group · Atul Tulshibagwale et al. · Jul 30, 2026
- The OAuth working group split over a token-binding draft that never says what DPoP lacks
Draft · · IETF Datatracker · Justin Richer et al. · Jul 28, 2026
- OAuth's draft for crossing trust domains is approved for publication and never says agent
Draft · · IETF OAuth Working Group · Arndt Schwenkschuster et al. · Jul 19, 2026
- Agent-audit draft now admits a call on the principal and the current agent, as RFC 8693 requires
Draft · · IETF Datatracker · Shameer Thaha et al. · Oct 19, 2026
- Okta and Google tie an agent's calls to the user, while GitHub's shared Copilot automations now act as Copilot
Release tracker · · 11 vendors' release notes · Oct 2026
- An OAuth client gets to name who vouches for it, and removing one waits on server caches
Draft · · IETF Datatracker · Karl McGuinness · Sep 28, 2026
- An OAuth draft lets the API, not the agent, describe the approval, and now name the key the token is bound to
Draft · · IETF Datatracker · Yaroslav Rosomakho et al. · Jun 25, 2026
- WIMSE's agent draft adds how an agent's access ends and where policy engines fit, without a new requirement
Draft · · IETF WIMSE Working Group · Pieter Kasselman et al. · Sep 15, 2026
- OAuth's SPIFFE draft opens metadata URLs to all three credentials and says what a self-served key cannot prove
Draft · · IETF Datatracker · Arndt Schwenkschuster et al. · Jun 15, 2026
- Raut's revised agent draft keeps token exchange out of the model's reach, and concedes the token carries no evidence of it
Draft · · IETF Datatracker · Ashay Raut · May 22, 2026
- OAuth's draft for token requests that wait on a person now gives the client a link for the user to approve
Draft · · IETF Datatracker · Guilherme de Oliveira Niero et al. · Sep 23, 2026
- Cross-App Access draft warns that one stolen sign-in token could reach every app the identity provider permits
Draft · · IETF Datatracker · Aaron Parecki et al. · May 21, 2026
- Drake's agent registry adds an opt-in brake: a registrar can block a transfer or key change until it releases it, never make one
Draft · · IETF Datatracker · Christopher Drake, 1id.com · Sep 25, 2026
- IETF workload practices draft describes single-audience JWTs in place of stored secrets and discourages token exchange
Draft · · IETF Datatracker · Arndt Schwenkschuster et al. · Sep 22, 2026
- WIMSE credentials -03: a valid signature proves trust-domain membership, not which workload is calling
Draft · · IETF Datatracker · Brian Campbell et al. · Jul 2, 2026
- AGTP checks that an agent ID is signed; binding it to the connection is an add-on in the author's patent notice
Draft · · IETF Datatracker · Chris Hood, Nomotic, Inc. · Jun 28, 2026
- Drake's agent registry names who may issue an agent's token, and its answer has no signature of its own
Draft · · IETF Datatracker · Christopher Drake, 1id.com · Sep 25, 2026
- One global registry for AI agent identities, and no one allowed to switch an identity off
Draft · · IETF Datatracker · Christopher Drake, 1id.com · Oct 27, 2026
- LinkedIn, Uber and State Farm already run SPIRE for workload identity, and each plans to extend it
Field signals · · 12 voices from the field · Nov 2024 to Oct 2026
- A cross-domain transaction-token grant now names AI agents as a use and keeps the call chain at home
Draft · · IETF Datatracker · George Fletcher et al. · Sep 10, 2026
- Visa’s agent-written patches still need human acceptance and attack-path validation
Podcast · · AI Security Podcast · How Visa Secures Trillions Using AI Agents & Open-Source Harnesses · Oct 2, 2026
- ERNW broke Kubernetes namespace tenancy three ways, using resources tenants are allowed to create
Video · · TROOPERS IT Security Conference · Uploaded August 12, 2026
- Datadog keeps tokens out of its AI agents' sandboxes: each holds an identity only the gateway accepts
Video · · fwd:cloudsec · Uploaded September 25, 2026
- Five places to put authorization in microservices, and why Drus says the classic gateway one does not scale
Video · · OWASP Foundation · Uploaded October 21, 2026
- From Level 2 up, OWASP's AI security standard asks for an identity per agent and a check on every MCP tool call
Video · · OWASP Foundation · Oct 21, 2026
- The IETF's stronger workload proof is built for the proxy in the middle, and it still leaves replay protection optional
Draft · · IETF Datatracker · Joseph A. Salowey et al. · Oct 20, 2026
- ChainIT's design has the payment rail rebuild each payment's hash before money moves; the paper reports no test
Paper · · arXiv · Jeremy Blackburn et al. · Oct 16, 2026
- Orange researchers would drop certificates from agent handshakes by putting post-quantum keys on a ledger
Paper · · arXiv · Karol Budzyn et al. · Oct 16, 2026
- An individual IETF draft takes a workload's role and group out of its name and puts them in separate metadata
Draft · · IETF Datatracker · Shlomo Zalman Heigh et al. · Oct 16, 2026
- Six companies' agent-auth draft, since adopted by the WIMSE group, keeps credentials out of the model's reach
Draft · · IETF Internet-Draft (individual submission, since adopted by the WIMSE working group) · Pieter Kasselman et al. · Jul 6, 2026
- Cloudflare's new OHTTP gateway will refuse traffic from its own Workers, so it never sees both the user and the request
Article · · Cloudflare Blog · Lara Schull · Oct 2, 2026
- OpenID's AuthZEN API can't say an agent acts for someone, and its policy service trusts whatever the app sends
Article · · OpenID Foundation · Omri Gazitt et al. · Jan 11, 2026
- An OAuth agent profile has the token server block any widening of scope, and leaves revoking the chain optional
Draft · · IETF Datatracker · Sanjeev Kumar, Orchestrum Technologies LLP · Aug 30, 2026
- An OAuth profile for AI agents makes every hand-off cut privileges, but a shorter expiry alone counts as a cut
Draft · · IETF Datatracker · Angel Cruz · Feb 7, 2026
- Anthropic asks for per-agent identity; its guide leaves Claude Code sub-agent credentials unspecified
Article · · Anthropic (Claude) · Anthropic · May 27, 2026
- Anthropic says agents should never use static API keys, yet its sub-agents can carry the parent's permissions
Article · · Anthropic · Anthropic · May 18, 2026
- OpenID Federation 1.0 lets each level of a trust chain only tighten the rules, and defines no revocation process
Article · · OpenID Foundation · Roland Hedberg et al. · Feb 17, 2026
- An end-to-end encrypted draft would hide an AI agent's task from the broker, but not who sent it or to whom
Draft · · IETF Datatracker · Hamdy Atakora, Imara Labs · Sep 21, 2026
- In Huawei's reworked OAuth draft, evidence signed by the token's subject can narrow access but never widen it
Draft · · IETF Datatracker · Cheng-Kang Chu et al. · Sep 1, 2026
- A2A 1.0 connects agents across companies and leaves out the person they act for
Article · · A2A Protocol (Linux Foundation) · A2A Protocol project et al. · May 28, 2026
- OWASP's agent Top 10 blames identity systems built for people, and does not say how it chose or ranked its risks
Article · · OWASP GenAI Security Project · John Sotiropoulos et al. · Dec 9, 2025
- NIST and CISA advise one-hour tokens, 90-day keys and hardware key storage; AI agents get one paragraph
Article · · NIST (CSRC) · Ryan Galluzzo et al. · Sep 15, 2026
- A survey rates only workload identity ready for agents, and argues no standard can tell what an agent intends
Paper · · arXiv · Takumi Otsuka et al. · Apr 25, 2026
- WIMSE mutual TLS -03 ties certificate acceptance to trust-domain anchors
Draft · · IETF Datatracker · Joseph A. Salowey et al. · Jul 6, 2026
- Transaction tokens are nearly a standard, and there is still no agreed place in them for the agent
Podcast · · Identity at the Center · #449 - Decoded - Transaction Tokens with George Fletcher · Sep 21, 2026
- OAuth handles an agent in one company, working while you watch. The OpenID paper says that is where it stops.
Article · · OpenID Foundation · Tobin South et al. · Oct 2025
- The IETF's workload-identity architecture gives AI agents one subsection, calling an agent a delegated workload
Draft · · IETF Datatracker · Joseph Salowey et al. · Jul 6, 2026
- The Agent Name Service draft was rebuilt on DNS, with a GoDaddy author, and no standards body has adopted it
Draft · · IETF Datatracker · Scott Courtney et al. · Apr 13, 2026
- IPC passes a delegation chain between services; its signature proves only the last signer
Draft · · IETF Datatracker · Ravi Kant Sharma, Ericsson · Jul 23, 2026
- A valid delegation chain cannot replace required human approval or proof of key possession
Draft · · IETF Datatracker · Karthik Rampalli, Glyphzero Labs · Jul 6, 2026
- A July OAuth draft keeps agent identity stable as keys rotate
Draft · · IETF Datatracker · Karl McGuinness · Jul 5, 2026
- A June OAuth draft logs each hand-off between AI agents, but the per-hop limits the act claim lacks are optional
Draft · · IETF Datatracker · Dapeng Liu et al. · Jun 8, 2026
- Google's agent registry went GA in June while Okta, SailPoint and Ping pulled agents into their own lists
Release tracker · · 11 vendors' release notes · Jun 2026
- Atlassian's first draft for offline delegation banned bearer handles; revision 05 just recommends sender binding
Draft · · IETF Datatracker · Larry Zhu et al. · May 22, 2026
- A 'decentralized' agent identity draft blocks risky calls when its Registry is down, and did:aip is taken
Draft · · IETF Datatracker · Paras Singla · Apr 17, 2026
- A proposed consent log for A2A and MCP records the terms an agent accepted, but the agent fills it in itself
Paper · · arXiv · Ravi Kiran Kadaboina · Apr 16, 2026
- AITH claims 4.7 million agent checks a second, but the test simulated its post-quantum signatures
Paper · · arXiv · Zhaoliang Chen · Apr 9, 2026
- A KubeCon demo moves MCP servers' OAuth checks into a gateway, safe only if nothing can reach a server directly
Video · · CNCF [Cloud Native Computing Foundation] · Uploaded March 24, 2026
- An agent identity draft signs every tool call, but never finished saying whom the agent answers to
Draft · · IETF Datatracker · James Cao et al. · Mar 16, 2026
- A cross-domain agent trust draft requires the call chain, then leaves its format to a version that never came
Draft · · IETF Datatracker · Daniel King et al. · Mar 15, 2026
- OAuth 2.1's October draft bans plain PKCE and adds browser-app rules; 2.1-only clients can fail on older servers
Draft · · IETF Datatracker · Dick Hardt et al. · Mar 2, 2026
- A Huawei agent draft keeps one 'master agent' as gatekeeper and drops the line that had servers re-check it
Draft · · IETF Datatracker · Yuan Ni et al. · Feb 28, 2026
- A draft binds workload credentials to their host via a local agent, and leaves that agent's compromise undecided
Draft · · IETF Datatracker · Ram Krishnan et al. · Feb 26, 2026
- OpenPort holds agent writes as drafts for an operator by default; its own tests check less than its spec asks
Paper · · arXiv · Genliang Zhu et al. · Feb 22, 2026
- Wisconsin researchers check each agent action against its history, in small tests with hand-written rules
Paper · · arXiv · Nils Palumbo et al. · Feb 18, 2026
- Google DeepMind wants agent authority to narrow at every hand-off, and misreads MCP's scopes on the way
Paper · · arXiv · Nenad Tomašev et al. · Feb 12, 2026
- MACAW Security's trust layer signs every agent call, but what stopped its prompt-injection test was a policy
Paper · · arXiv · Mohan Rajagopalan et al. · Feb 11, 2026
- A China Mobile draft would end an agent's token when its task ends, if a webhook says so
Draft · · IETF Datatracker · Meiling Chen et al. · Feb 4, 2026
- A secure-MCP proposal registers every agent and tool centrally, and never mentions MCP's own OAuth rules
Paper · · arXiv · Xinyi Hou et al. · Feb 1, 2026
- In February Okta let AI agents reach its management APIs over MCP; Cloudflare added controls on MCP connections
Release tracker · · 7 vendors' release notes · Feb 2026
- ACME's device-attestation draft now advises leaving device IDs out of certificates and drops a key-export rule
Draft · · IETF Datatracker · Brandon Weeks et al. · Jan 29, 2026
- Faramesh holds each agent action for a signed permit; its bypass tests assume no path around the gate
Paper · · arXiv · Amjad Fatmi · Jan 25, 2026
- Uber reports authorizing over 2 million service-to-service connections a second after staged rollout
Video · · CNCF [Cloud Native Computing Foundation] · Uploaded November 24, 2025
- State Farm moved SPIRE from many token issuers to one, then hit an AWS key quota and a 15-character name limit
Video · · CNCF [Cloud Native Computing Foundation] · Nov 24, 2025
- CORAL's public agent server rejected forged messages but let a wrong key open the session stream
Paper · · arXiv · Yedidel Louck et al. · Nov 5, 2025
- AAGATE maps NIST's AI risk framework onto Kubernetes, and its paper never times the 'millisecond kill switch'
Paper · · arXiv · Ken Huang et al. · Oct 29, 2025
- Ericsson researchers would check every query a telecom network agent sends to its knowledge base
Paper · · arXiv · Loay Abdelrazek et al. · Oct 22, 2025
- WIMSE leaves its application proof choice open, with different integrity coverage
Draft · · IETF Datatracker · Brian Campbell et al. · Oct 16, 2025
- A refresh-token thief who waits for the app to close slips past reuse detection
Article · · Auth0 Blog · Maria Vasilevskaya, Okta · Oct 8, 2025
- SPIFFE can authenticate an OAuth client; trust and registration still come first
Draft · · IETF Datatracker · Arndt Schwenkschuster et al. · Oct 3, 2025
- One author's OpenID Connect for Agents proposal checks each delegation hop but makes the chain optional
Paper · · arXiv · Subramanya Nagabhushanaradhya · Sep 30, 2025
- OpenID's credential issuance standard is OAuth for wallets, and assumes a trusted wallet is an app on a phone
Article · · OpenID Foundation · Torsten Lodderstedt et al. · Sep 16, 2025
- Auth0's DPoP explainer leaves out the access-token hash that RFC 9449 requires on every API call
Article · · Auth0 Blog · Andrea Chiarelli · Aug 25, 2025
- A 'provable' bound on agent-memory injection assumes independent layers and fills in none of its detection rates
Paper · · arXiv · Ken Huang et al. · Aug 17, 2025
- A survey of MCP and A2A attacks pairs each identity threat with a fix, and tests none of them
Paper · · arXiv · Mohamed Amine Ferrag et al. · Jun 29, 2025
- ETDI would sign MCP tool definitions against lookalikes, but leaves open who vouches for the publisher's key
Paper · · arXiv · Manish Bhatt et al. · Jun 2, 2025
- The first Agent Name Service paper puts capabilities in the name and leaves protocol translation and governance out
Paper · · arXiv (cs.CR preprint 2505.10609) / OWASP Agentic Security Initiative · Ken Huang et al. · May 15, 2025
- An A2A threat model flags the Agent Card as an attack path, and its example flow never passes on the user's identity
Paper · · arXiv · Idan Habler et al. · Apr 23, 2025
- MCP Guardian wraps tool calls in token and regex checks, leaving poisoned servers and agent IDs open
Paper · · arXiv · Sonu Kumar et al. · Apr 17, 2025
- An early MCP security checklist was never tested, and the protocol has since adopted only part of it
Paper · · arXiv · Vineeth Sai Narajala et al. · Apr 11, 2025
- A rogue OAuth server can collect a client's signed assertion and replay it at an honest server the client also uses
Article · · IACR Cryptology ePrint Archive · Pedram Hosseyni et al. · Apr 7, 2025
- RFC 9728 tells clients where an API's tokens come from and leaves most of the trust decision to them
Article · · RFC Editor · Michael B. Jones et al. · Apr 2025
- FAPI 2.0 issues only sender-constrained access tokens and leaves public clients out
Article · · OpenID Foundation · Daniel Fett et al. · Feb 22, 2025
- RFC 9700 bans OAuth's password grant and loose redirect matching; binding access tokens stays a SHOULD
Article · · IETF (RFC Editor) · Torsten Lodderstedt et al. · Jan 2025
- In GNAP (RFC 9635), a client is known by its key, and tokens stay key-bound unless the server flags them bearer
Article · · RFC Editor · Justin Richer et al. · Oct 1, 2024
- In May 2023, Parecki described OAuth 2.1 as consolidation and DPoP as token protection
Video · · Identiverse - A CRA Resource · Jun 17, 2024
- DPoP token binding depends on checks at the resource server
Article · · RFC Editor · Daniel Fett et al. · Sep 2023
- CIBA's human-approval step carries a short matching code, not a description of the action
Article · · OpenID Foundation · Gonzalo Fernandez Rodriguez et al. · Sep 1, 2021
- RFC 8705 lets OAuth bind tokens to a client certificate, and leaves the proxy in front of the API to the deployer
Article · · RFC Editor · Brian Campbell et al. · Feb 28, 2020
- In draft FAPI, token binding did not make phished tokens useless: the attacker had the bound client spend them
Paper · · arXiv · Daniel Fett et al. · Jan 31, 2019
- RFC 6750 tokens work for whoever holds them; RFC 9700 now urges key binding and bars them from query strings
Article · · RFC Editor · Michael B. Jones et al. · Oct 1, 2012
- RFC 6749 admits a server can't tell who presents a token; the fixes arrived in 2020 and 2023
Article · · RFC Editor · D. Hardt et al. · Oct 2012
- Microsoft's 2023 keynote: workload standards should carry identity across service calls first, policy later
Video · · Identiverse - A CRA Resource · Recorded May 31, 2023 · Uploaded June 17, 2024
Related terms
What appears alongside mTLS in the same briefings.
OAuth SPIFFE Client AuthenticationSender-constrainingX.509-SVIDDPoPJWTSPIFFEOAuthOpenID Connect
Was this explainer useful?
Share this explainer
Pass it on. Every claim has a permanent number, so what you share today still points at the same words next year.