[
https://issues.apache.org/jira/browse/CAMEL-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815222#comment-16815222
]
Daniel del Castillo commented on CAMEL-11030:
---------------------------------------------
Any updates on this ticket? I'm looking to read secrets, not just credentials,
from Vault and then use them downstream in the route. I think a {{vault:}}
component may be most suitable for this?
> 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
> Priority: Major
> Fix For: 3.0.0
>
>
> 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
(v7.6.3#76005)
