[
https://issues.apache.org/jira/browse/AMBARI-9480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307802#comment-14307802
]
Robert Nettleton commented on AMBARI-9480:
------------------------------------------
I've filed AMBARI-9501 to track the formatting issues related to these files
being created with tab characters included.
> Ranger password properties are incorrectly included in Blueprint export
> -----------------------------------------------------------------------
>
> Key: AMBARI-9480
> URL: https://issues.apache.org/jira/browse/AMBARI-9480
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Fix For: 2.0.0
>
> Attachments: AMBARI-9480.patch.2
>
>
> Some new security configuration properties related to Ranger have been added
> to the stack definitions. Some of these properties are actually password
> configuration properties, but are not currently marked as such in the
> metadata.
> This causes exporting a Blueprint from a running cluster to include this
> password information in the exported Blueprint.
> Some of the Ranger-related password properties found across the stack are:
> REPOSITORY_CONFIG_PASSWORD
> SSL_TRUSTSTORE_PASSWORD
> SSL_KEYSTORE_PASSWORD
> The Ambari stack definitions need to be updated, such that these properties
> are marked as being of propert-type "PASSWORD". This will allow the
> Blueprint configuration processor to determine that these are indeed password
> properties, and should not be included in an exported Blueprint.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
