You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Karol Krawczyk (Jira)" <ji...@apache.org> on 2026/09/22 04:08:00 UTC
[jira] [Work started] (CAMEL-24637) camel-jms: implement SecretRotationAware to re-authenticate on secret rotation
[ https://issues.apache.org/jira/browse/CAMEL-24637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on CAMEL-24637 started by Karol Krawczyk.
----------------------------------------------
> camel-jms: implement SecretRotationAware to re-authenticate on secret rotation
> ------------------------------------------------------------------------------
>
> Key: CAMEL-24637
> URL: https://issues.apache.org/jira/browse/CAMEL-24637
> Project: Camel
> Issue Type: Sub-task
> Components: camel-jms
> Reporter: Andrea Cosentino
> Assignee: Karol Krawczyk
> Priority: Major
>
> Sub-task of CAMEL-24636.
> Adopt the {{SecretRotationAware}} SPI in camel-jms.
> {{JmsComponent#setUsername}} and {{setPassword}} delegate to a shared {{JmsConfiguration}}, whose values are resolved from property placeholders once at configure time. The {{ConnectionFactory}} itself is normally a registry bean (often a pooled one) created at bootstrap with the credentials valid at that moment.
> Neither is refreshed by {{RouteController.reloadAllRoutes()}}, so after a secret rotation the component keeps presenting the old credentials.
> On {{onSecretRotation}} the component should re-resolve its configured username and password and re-authenticate the connection factory in place, closing and re-establishing pooled connections as needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)