[
https://issues.apache.org/jira/browse/AMBARI-11142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Nettleton resolved AMBARI-11142.
---------------------------------------
Resolution: Duplicate
Closing as a duplicate of an earlier issue that has been re-opened for Ambari
2.1, AMBARI-9480.
> 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
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> 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)
