[
https://issues.apache.org/jira/browse/AMBARI-22571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296195#comment-16296195
]
Robert Levas commented on AMBARI-22571:
---------------------------------------
Committed to trunk
{noformat}
commit be0e87bef52458955eddf1b824e6c5ddc6f31de6
Author: Sandor Molnar <[email protected]>
Date: Mon Dec 18 23:38:29 2017 -0500
{noformat}
[~smolnar], This has been committed to the trunk. You can resolve this JIRA and
close the ReviewBoard.
> Handle passwords/sensitive data in Ambari configuration properties
> ------------------------------------------------------------------
>
> Key: AMBARI-22571
> URL: https://issues.apache.org/jira/browse/AMBARI-22571
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Minor
> Labels: config, security
> Fix For: trunk
>
> Attachments: AMBARI_22571_trunk_01.patch
>
>
> Passwords and other sensitive data stored as values to properties in Ambari
> configurations need to be masked or not stored in cleartext.
> For example,
> {{ldap-configuration/ambari.ldap.connectivity.trust_store.password}} and
> ldap-{{configuration/ambari.ldap.connectivity.bind_password}}.
> If the Ambari credential store is enabled (which might be by default as of
> Ambari 3.0.0), the sensitive date can be stored there like we do when
> sensitive data is to be stored in the ambari.properties file - see
> {{org.apache.ambari.server.security.encryption.CredentialStoreService}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
