[
https://issues.apache.org/jira/browse/FELIX-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319685#comment-14319685
]
Chetan Mehrotra commented on FELIX-4599:
----------------------------------------
{quote}
>From this I deduct two requirements:
# sensitive information should not be put in plain text to disk
# sensitive information should not be visible to any user in plain text (web
console, JMX etc.)
{quote}
+1 > probably we can support both.
Requirement #1 is easy as that can be done in a central place by expose some
extension point in {{FilePersistenceManager}} or providing an
{{EncryptingPersistenceManager}} wrapper for
[PersistenceManager|https://github.com/apache/felix/blob/trunk/configadmin/src/main/java/org/apache/felix/cm/PersistenceManager.java]
Requirement #2 is would involve new api and co-operation from client bundles
who consume the config to make use of the API to decrypt config
> Support Encryption Of Configuration Properties
> ----------------------------------------------
>
> Key: FELIX-4599
> URL: https://issues.apache.org/jira/browse/FELIX-4599
> Project: Felix
> Issue Type: New Feature
> Components: Configuration Admin
> Reporter: Dominique Jäggi
>
> Currently it is not possible to define configuration properties, the contents
> of which should be automatically encrypted upon save by the configuration
> admin.
> An example would be a mail server configuration, where SMTP credentials must
> specified and the password should be encrypted upon saving the configuration.
> The encrypted password should then be accessible and decryptable in the
> component to which the configuration is bound.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
