[
https://issues.apache.org/jira/browse/CAMEL-25458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-25458.
--------------------------------------
Resolution: Fixed
Fixed in 4.24.0 (main) via https://github.com/apache/camel/pull/28155 and in
4.22.3 (camel-4.22.x) via https://github.com/apache/camel/pull/28221. camel-a2a
is not on camel-4.18.x.
_Claude Code on behalf of Andrea Cosentino_
> camel-a2a - improve how the consumer derives the caller profile
> ---------------------------------------------------------------
>
> Key: CAMEL-25458
> URL: https://issues.apache.org/jira/browse/CAMEL-25458
> Project: Camel
> Issue Type: Bug
> Components: camel-ai
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.22.3, 4.24.0
>
>
> The A2A consumer validates the security schemes declared in the agent card
> and builds the caller profile that it exposes to the route as the
> {{CamelA2AUserProfile}} exchange property. Improve this:
> * Rework how the caller profile is derived from the validated schemes, so
> that it always reflects the authenticated caller.
> * Make the OAuth token validation result
> ({{CamelOAuthTokenValidationResult}}) available on the exchange the route
> processes, as the component documentation describes. Today it is only set on
> the incoming HTTP exchange, so the route never sees it.
> * Document how the caller profile is derived for each supported scheme type.
> _Claude Code on behalf of Andrea Cosentino_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
