[jira] [Resolved] (CAMEL-19508) Add possibility to supply custom headers in LRAClient requests

["Johannes Boßle (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-19508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johannes Boßle resolved CAMEL-19508.
------------------------------------
    Fix Version/s: 3.x
                   4.0.0
       Resolution: Implemented

This improvement has been implemented by [#10505|https://github.com/apache/camel/pull/10505] and will be available also in main for version 4 ([https://github.com/apache/camel/commit/238ec905e46b7e0a737925e73569f841556845dd)]

Please feel free to re-open this issue and adjust to your needs.

> Add possibility to supply custom headers in LRAClient requests
> --------------------------------------------------------------
>
>                 Key: CAMEL-19508
>                 URL: https://issues.apache.org/jira/browse/CAMEL-19508
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-lra
>    Affects Versions: 3.x, Future
>            Reporter: Johannes Boßle
>            Priority: Major
>             Fix For: 3.x, 4.0.0
>
>
> Within the apache camel Saga EIP, there is currently no obvious possibility to supply headers like "Authentication", when you are using a lra-coordinator with the LRASagaService. If you want to use e.g. Narayana in a secure way with authentication enabled (the Narayana LRA coordinator supports JSON Web Tokens and there's even a [quickstart|https://github.com/jbosstm/quickstart/blob/main/rts/lra-examples/lra-jwt/wildfly/README.md] to help users get started), there is currently no easy possibility to pass on authentication information.
> As general extension, this can be even extended to supply (additional) headers in any form to the requests.
> The implementation class LRAClient is taking care of making the calls to the coordinator and uses a java.net.http.HttpClient for it. So the solution could be, to override the default behavior of the LRAClient and to give developers/users the possibility to hook into creating the HttpRequest and supply additional values.
> Intentional use-case: add a header `Authorization` to every request agains the lra-coordinator
> Generic use-case: allow to add custom headers to requests against the lra-coordinator



--
This message was sent by Atlassian Jira
(v8.20.10#820010)