Upgrading and Migrating A2A Connector to Version 1.x

There is now a clear distinction in the naming between client and server operations/sources.

A2A Connector now supports the new A2A Client - Send Stream Message, A2A Client - Task Resubscribe, A2A Server - Send Push Notification, A2A Server - Update Task Artifact, and A2A Server - Update Task Status operations.

A2A Connector now supports the new A2A Server - On Task Stream Listener source.

In the A2A Server - On Push Notification Set Listener source, Response Timeout is now Push notification request timeout, and Response Timeout Unit is now Request Timeout Unit.

Push notifications on the A2A server side are no longer supported unless the A2A Server - On Push Notification Set Listener source is defined.

The server now performs out-of-the-box context ID and task ID validations for tasks associated with the application.

The server now supports task cancellation via the tasks/cancel method.

A2A Connector now includes the A2A:TASK_NOT_CANCELABLE and A2A:UNSUPPORTED_OPERATION errors for all operations.

A2A Connector no longer includes the A2A:TASK_ALREADY_COMPLETED error for all operations.

A2A Connector now uses the A2A Java SDK for request and response validations, which enhances reliability.

In the Server connection type, Card is replaced with either Card Json or Card Path to define the agent card.

The Agent Card, Agent Skill, Agent Capabilities, Agent Extension, Agent Provider, Security Requirement, Http Security Scheme, Api Key Security Scheme, Oauth2 Security Scheme, Oauth2 Flows, Implicit Oauth2 Flows, Oauth2 Scope, Password Oauth2 Flows, Client Credentials Oauth2 Flows, Authorization Code Oauth2 Flows, and Open Id Connect Security Scheme types are no longer supported.

Introduction to Anypoint Connectors

MuleSoft Help Center