Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 17 Mar 2017 09:00:51 +0000 (UTC)
From: "Luca Burgazzoli (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.13056936.1489741243000.46886.1489741251226@Atlassian.JIRA>
In-Reply-To: <JIRA.13056936.1489741243000@Atlassian.JIRA>
References: <JIRA.13056936.1489741243000@Atlassian.JIRA> <JIRA.13056936.1489741243019@jira-lw-us.apache.org>
Subject: [jira] [Created] (CAMEL-11030) Add a vault service to manage
 secrets
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 17 Mar 2017 09:01:00 -0000

Luca Burgazzoli created CAMEL-11030:
---------------------------------------

             Summary: 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
             Fix For: Future


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
(v6.3.15#6346)