[ 
https://issues.apache.org/jira/browse/CAMEL-24639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18115917#comment-18115917
 ] 

Guillaume Nodet commented on CAMEL-24639:
-----------------------------------------

This issue is being investigated by a coding agent (on behalf of gnodet).

The *SecretRotationAware* SPI (merged in CAMEL-24636 / PR #26166, commit 
0b46030091bb) is confirmed present on main. *HttpComponent* does not yet 
implement it.

Plan: implement _onSecretRotation_ in HttpComponent to re-resolve the 
authentication options 
(authUsername/authPassword/authDomain/proxyAuthUsername/proxyAuthPassword) and 
rebuild the internal HttpClientConfigurer that carries the CredentialsProvider 
— without recreating the shared connection manager.

_Note: This comment was generated by an AI coding agent and requires manual 
verification._

> camel-http: implement SecretRotationAware to refresh credentials on rotation
> ----------------------------------------------------------------------------
>
>                 Key: CAMEL-24639
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24639
>             Project: Camel
>          Issue Type: Sub-task
>          Components: camel-http
>            Reporter: Andrea Cosentino
>            Assignee: Guillaume Nodet
>            Priority: Major
>
> Sub-task of CAMEL-24636.
> Adopt the {{SecretRotationAware}} SPI in camel-http.
> {{HttpComponent}} can hold a shared {{HttpClientConnectionManager}} and a 
> {{HttpClientConfigurer}}, and component-level authentication options are 
> resolved from property placeholders once at configure time. A context reload 
> clears the endpoint registry but leaves the component and its connection 
> manager in place, so rotated credentials are not picked up.
> On {{onSecretRotation}} the component should re-resolve its authentication 
> configuration and refresh the credentials provider used by the client, so 
> that subsequent requests authenticate with the new secret without recreating 
> the shared connection manager.
> Note that endpoint-level options are re-resolved as a side effect of the 
> endpoint registry being cleared; this sub-task is specifically about 
> component-level and shared-client state.



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

Reply via email to