[
https://issues.apache.org/jira/browse/CAMEL-25584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18126486#comment-18126486
]
Andrea Cosentino commented on CAMEL-25584:
------------------------------------------
Merged to main via https://github.com/apache/camel/pull/27725 (squash commit
86224cd178c3, ships in 4.24.0). The 4.22.x and 4.18.x backports are still to
come, so this issue stays open until they merge.
_Claude Code on behalf of oscerd_
> camel-lra - only join LRAs hosted by the configured LRA coordinator
> -------------------------------------------------------------------
>
> Key: CAMEL-25584
> URL: https://issues.apache.org/jira/browse/CAMEL-25584
> Project: Camel
> Issue Type: Improvement
> Components: camel-lra
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.18.6, 4.22.2, 4.24.0
>
>
> When a message with a {{Long-Running-Action}} header reaches a saga route,
> the LRA saga service joins that LRA by calling the URL in the header, and the
> saga component's complete/compensate operations close or cancel it the same
> way. The URL is not checked against the configured LRA coordinator.
> * accept a {{Long-Running-Action}} only when its URL is under the configured
> coordinator ({{coordinatorUrl}} + {{coordinatorContextPath}}); otherwise the
> exchange fails with a clear error
> * new option {{allowedCoordinatorUrls}} (also
> {{camel.lra.allowedCoordinatorUrls}}): further coordinator URLs to accept,
> e.g. when services reach the same coordinator under different host names
> * upgrade-guide note: a {{Long-Running-Action}} from another coordinator is
> now rejected
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
