You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/02 09:26:00 UTC

[jira] [Updated] (CAMEL-11030) Add a vault service to manage secrets

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

Claus Ibsen updated CAMEL-11030:
--------------------------------
    Fix Version/s: 3.19.0
                       (was: 3.x)

> 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.19.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
(v8.20.10#820010)