You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Robert Nettleton (JIRA)" <ji...@apache.org> on 2015/05/14 22:33:59 UTC

[jira] [Created] (AMBARI-11142) Ranger password properties incorrectly appear in exported Blueprint

Robert Nettleton created AMBARI-11142:
-----------------------------------------

             Summary: Ranger password properties incorrectly appear in exported Blueprint
                 Key: AMBARI-11142
                 URL: https://issues.apache.org/jira/browse/AMBARI-11142
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.0.0
            Reporter: Robert Nettleton
            Assignee: Robert Nettleton
            Priority: Critical
             Fix For: 2.1.0


When a Blueprint is exported from a running cluster, there are some Ranger-related properties that appear in the Blueprint, even though these fields are marked as having the "PASSWORD" type in the stack metadata.

This is due to the fact that these passwords are not marked as "required", which is necessary for the Blueprints processor to remove the properties from the exported Blueprint.  The Ranger passwords are not marked as "required" because they are only required when SSL is enabled.  This represents a "conditional password" that is only relevant when certain services are enabled.  This type of conditional field is not modelled in the stack definitions.  

In the short-term, the Blueprints configuration processor should be modified in order to filter out any Ranger password properties that fit this category.  




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)