live wire
AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLMAI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM
upstreambeat.ai
releaseAI

A2A Java SDK 1.2 closes task-authorization gaps and changes migration paths

The Quarkus-backed Java implementation adds fail-closed checks and stream controls, but adopters must account for three breaking changes.

By The News Desk· Aug 18, 2026

The A2A Java SDK 1.2.0.Final release tightens authorization around referenced tasks, adds controls for long-lived task streams and changes several APIs that agent-platform teams may already depend on. The project describes the SDK as the official Java implementation of the A2A Protocol, with Quarkus as its reference runtime and Quarkus applications across its examples.

What changed

The most consequential change is an authorization check on tasks named through referenceTaskIds. The release post says earlier versions populated those tasks in RequestContext without first checking whether the caller could read them. That allowed an unauthorized caller to probe for a task through streaming-message or task-subscription operations.

Version 1.2 applies read checks across JSON-RPC, gRPC and REST transports. Its in-memory task store now also fails closed when authorization is configured but no call context is available, matching the behavior of the JPA-backed store. A new TaskAuthorizationProvider.checkReadAccess() helper exposes that policy for custom stores, while the authorization decorator can now be wired outside CDI runtimes such as Spring.

The release also introduces TaskStreamLifecycleHook. Applications can observe subscriptions, disconnections and processed events, then close all streams for a task. The project points to timeouts, subscriber limits and cleanup after clients disconnect as intended uses. The hook is wired through the in-memory, main event-bus and replicated queue-manager paths.

Who is affected

Teams upgrading from 1.1.0.Final need to treat this as more than a dependency refresh. The project flags three breaking changes. The request-handler authorization method is renamed and gains call-context and operation parameters; DefaultRequestHandler.create() gives way to a builder; and read authorization is enforced when referenced tasks are resolved.

Custom task stores, non-CDI integrations and applications that assumed referenced tasks would be readable without an explicit authorization decision deserve particular scrutiny. The release also changes default behavior by populating referenced tasks for CDI users unless a2a.request-context.populate-referred-tasks=false is set.

What to do

Before updating the BOM to 1.2.0.Final, review the migration section and test task lookup through every transport your agent exposes. Confirm that custom authorization providers receive a usable call context and that custom stores deny access when they cannot make a decision.

Applications with streaming clients should also test subscription teardown and task completion under load before adopting the lifecycle hook. The release includes fixes for streaming history length, task and context identifiers in emitted messages, and a Vert.x HTTP-client race, so regression tests should cover both access control and event delivery rather than authorization alone.

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.