[
https://issues.apache.org/jira/browse/CAMEL-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312294#comment-17312294
]
Zoran Regvart commented on CAMEL-11030:
---------------------------------------
I think it's important to have a API/SPI to notify of any changes to the
credentials. Ideally we would have component or endpoint property metadata that
indicates for what properties notifications are received. I'm not sure if that
way of implementing this would be (really) difficult, it would mean that Camel
core might need to keep track of from where the value of a property was
received.
> Add a vault service to manage secrets
> -------------------------------------
>
> Key: CAMEL-11030
> URL: https://issues.apache.org/jira/browse/CAMEL-11030
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Luca Burgazzoli
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 3.x
>
>
> Lot of components these days are supposed to manage secrets such as auth
> tokens etc. but as there's no common support in camel each component is
> implementing the same concept which increase the maintenance cost.
> It would be nice to have a vault service in camel-core so that components can
> leverage and extend it, some ideas/examples:
> - to store auth tokens and delegate to the vault the notification about
> expiration and renewal when needed (by registering some functions/callbacks)
> - to provide different backends like kubernetes secrets, hashicorp's vault,
> - to provide different workflow (i.e. JSON Web Token)
> - to use the vault as properties source if someone prefix a property with
> vault like {{vault:db.password}}
> The interface should be as simple as possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
