ChangeGamer

A2A Authentication Schemes: Which to Declare in Your Agent Card

Part 5 of A2A in practice: agent-to-agent interoperability · 1,123 words · ~5 min read · published · updated · Markdown variant

The five security scheme families an A2A Agent Card can declare (API key, HTTP auth, OAuth 2.0, OpenID Connect, mutual TLS), an inference-labelled rule for choosing one, and how a client handles auth-required tasks.

In short

  • An A2A Agent Card declares how clients must authenticate through securitySchemes plus security requirements, and the A2A reference lists five scheme families: API key, HTTP auth, OAuth 2.0, OpenID Connect and mutual TLS.
  • A2A v1.0.0 modernised its OAuth 2.0 flows by adding device code and PKCE, according to the A2A reference in the ChangeGamer corpus, which was last updated on 27 October 2026.
  • The TASK_STATE_AUTH_REQUIRED state pauses an A2A task for the client, so, as inference, a client should treat it as a recoverable request for credentials and not as a failure.
  • Which authentication scheme production A2A agents actually use could not be confirmed from the corpus, so any claim that one scheme dominates is unverified.
  • Choosing an A2A scheme is, as inference, a question of who the caller acts for: workload identity suits a service calling in its own right, while delegated authority needs a scoped OAuth grant.

Part of the The A2A Protocol in Practice: Agent Cards, Tasks, Auth and When You Need It guide.


To pick an A2A authentication scheme, choose from the five families an Agent Card can declare, then make sure a client can satisfy the one you choose. The A2A protocol reference (updated 27 October 2026) lists them. The pillar shows where authentication appears in the protocol; this article is about the decision: which scheme to declare, and what a calling client does to meet it.

Which authentication schemes can an A2A Agent Card declare?

The five families (API key, HTTP auth, OAuth 2.0, OpenID Connect and mutual TLS) and the v1.0.0 OAuth changes are listed in the pillar's authentication section, so they are not repeated here. What matters for the choice is what the reference leaves out: it gives no placement or format detail for API keys, no sub-type detail for HTTP auth, no flow detail for OpenID Connect and no certificate detail for mutual TLS. It also does not say how any family maps onto the three bindings; the bindings article covers what differs on the wire, and credential passing per binding is not stated here.

How should you choose a scheme? (inference)

Choose by who the caller is acting for, because the identity reference splits agent authentication into two layers. Everything in this table is inference, mapping that split onto A2A's families; the specification gives no such guidance.

The agent identity reference (updated 17 July 2026) separates workload identity (what the agent is) from delegated authority (permission to act for a human or organisation), and says conflating them causes most agent-auth mistakes.

Situation Lean toward (inference) Reason (inference)
Your own services call a partner agent as themselves Mutual TLS, or OAuth 2.0 Workload identity: the caller proves what it is
An agent acts for a human user OAuth 2.0 or OpenID Connect Delegated authority needs a scoped grant, not a forwarded user token
A human must approve access interactively on a limited device OAuth 2.0 device code v1.0.0 added it for exactly this shape of flow
Early prototype, one known caller API key Cheapest to run, but the identity reference warns that static keys shared across instances cannot be pinned to one process or rotated automatically
You already issue enterprise single sign-on OpenID Connect Reuses an identity provider you operate

Declare only the schemes you will operate and monitor. As inference, a card that lists five schemes forces every caller to guess which one you actually enforce. The identity article covers the underlying distinction, including SPIFFE-issued workload credentials, in how AI agents prove identity and delegated authority.

How does a client satisfy a declared scheme?

A client reads the card's securitySchemes and security requirements, obtains matching credentials, and presents them before calling. The pillar states the same duty; the corpus gives no further mechanics.

A workable client sequence, all of it inference beyond the first step:

  1. Fetch the card from /.well-known/agent-card.json.
  2. Read the security requirements and pick a requirement set you can meet.
  3. Obtain credentials out of band or through the declared flow (for OAuth 2.0, the flow the card names).
  4. Cache the credential only for its lifetime; never log it.
  5. Call the agent, and handle an auth-required task as described below.

Scheme parameters beyond the family name, such as token endpoints or scopes, are not described in the corpus. Read them from the card and the specification, not from this article.

How do securitySchemes relate to the extended card?

The securitySchemes block belongs in the public card, because a client must learn how to authenticate before it can (inference). The extended card is the other half: if extendedAgentCard is true, an authenticated client can fetch fuller details. The Agent Card design article works through that split, so it is not restated here.

What should a client do on TASK_STATE_AUTH_REQUIRED?

A client should treat TASK_STATE_AUTH_REQUIRED as a pause awaiting credentials, not an error. The reference says the state pauses the task for the client; the task lifecycle article places it among the interrupted states.

Everything past "pauses for the client" is inference. A reasonable pattern:

Do not hand an agent the user's own token to satisfy the pause; the identity reference calls that an anti-pattern because it invites overbroad access and confused-deputy replay.

What mistakes should you avoid when declaring schemes? (inference)

Avoid declaring a scheme you cannot revoke, rotate or audit; every point here is inference from the identity reference, not A2A specification text.

What does the corpus not say about A2A authentication?

The corpus does not say which scheme production agents use, how credentials travel per binding, how failures are signalled, or how a task resumes after auth-required. As of 3 November 2026, the A2A reference records no HTTP status mapping, no authentication error codes and no adoption figures, so this article states none.

Two neighbouring questions are separate. Card signing is optional; authentication proves the caller to the callee, not the reverse. Verifying a remote agent is covered in trusting a remote agent, and how credentials propagate across delegation hops in credential propagation.

Does ChangeGamer implement A2A authentication?

No. As of 2 November 2026, the site speaks MCP over JSON-RPC and implements no A2A endpoint, as the bindings article records, so the guidance above is reasoning from the reference, not from running an A2A security scheme in production.

Frequently asked questions

What authentication does A2A support?
A2A Agent Cards can declare API key, HTTP auth, OAuth 2.0, OpenID Connect and mutual TLS security schemes, according to the A2A reference in the ChangeGamer corpus. The card lists the schemes and the security requirements a client must meet before calling the agent.
Does A2A support OAuth 2.0 device code and PKCE?
A2A v1.0.0, released on 12 March 2026, modernised its OAuth 2.0 flows by adding device code and PKCE, according to the A2A reference in the ChangeGamer corpus. The reference does not detail the flow mechanics, so read the specification before implementing them.
What should an A2A client do when a task becomes auth-required?
An A2A client should treat TASK_STATE_AUTH_REQUIRED as a pause awaiting credentials, not as a failure. The reference says only that the state pauses the task for the client; how the task resumes is not in the corpus, so that handling pattern is inference.
Which authentication scheme do production A2A agents use most?
Which authentication scheme production A2A agents use most could not be confirmed from the ChangeGamer corpus as of November 2026. The reference lists the supported families but publishes no adoption figures, so treat any popularity claim as unverified.

#a2a #authentication #oauth #security-schemes #agent-card #agent2agent

Put this corpus inside your own agents

This guide is free and stays free. The reference corpus behind it — machine-readable contracts, verified primary sources, continuously refreshed — is the paid product: a €5 starter key unlocks every premium reference for one agent via API; a €25 corpus license delivers the full corpus as RAG / fine-tuning data with an explicit AI-use grant; the €150 enterprise license adds commercial redistribution rights.

Agents: this page as Markdown · JSON · offers at /api/pricing.json · payment methods at /api/payment.json · single-resource access via HTTP 402 (how that works)