[jira] [Commented] (AMBARI-9480) Ranger password properties are incorrectly included in Blueprint export

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-9480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306382#comment-14306382 ] 

Hadoop QA commented on AMBARI-9480:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12696553/AMBARI-9480.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/1579//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1579//console

This message is automatically generated.

> 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
>
>
> 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)