Return-Path: 
 <dev-return-32506-apmail-ambari-dev-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-dev-archive@www.apache.org
Delivered-To: apmail-ambari-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8CA3B11083
	for <apmail-ambari-dev-archive@www.apache.org>;
 Tue,  1 Jul 2014 20:38:25 +0000 (UTC)
Received: (qmail 17867 invoked by uid 500); 1 Jul 2014 20:38:25 -0000
Delivered-To: apmail-ambari-dev-archive@ambari.apache.org
Received: (qmail 17780 invoked by uid 500); 1 Jul 2014 20:38:25 -0000
Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ambari.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ambari.apache.org>
List-Post: <mailto:dev@ambari.apache.org>
List-Id: <dev.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list dev@ambari.apache.org
Received: (qmail 17584 invoked by uid 99); 1 Jul 2014 20:38:25 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2014 20:38:25 +0000
Date: Tue, 1 Jul 2014 20:38:25 +0000 (UTC)
From: "Mahadev konar (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12724808.1404245924952.83146.1404247105252@arcas>
In-Reply-To: <JIRA.12724808.1404245924952@arcas>
References: <JIRA.12724808.1404245924952@arcas>
Subject: [jira] [Commented] (AMBARI-6344) Views: Add <mask> optional
 attribute to <parameter> in view.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Mahadev konar commented on AMBARI-6344:
---------------------------------------

+1 for the patch.

> Views: Add <mask> optional attribute to <parameter> in view.xml
> ---------------------------------------------------------------
>
>                 Key: AMBARI-6344
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6344
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.7.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-6344.patch
>
>
> Certain parameters that ambari will persist should be optionally masked. This will be useful in cases where an instance parameter is a password or something similar. By having this setting available, Ambari can handle storing the parameter in a non-plain-text way, as well, the UI for configuring view instances will know to mask the parameter (input type=password). 
> 1. There should be a default masking implementation (can be something simple like base64 encode for example) that for a parameter that has the <mask> attribute, the parameter will be masked.
> <parameter>
> <mask>true</mask>
> ...
> </parameter>
> 2. There is a more advanced option where a view also specifies the <mask-class> to customize the way parameters are read/written. The class (implements an interface, maybe) for callback on read/write of the parameter so view developers can implement a special way to encrypt/decrypt.
> <mask-class>my.custom.class</mask-class>
> <parameter>
> <mask>true</mask>
> ...
> </parameter>
> Note: changing the terminology to mask (from encrypt) since encrypt sets a certain expectation. Masking in the default sense is good convenience to provide to views, and if they want more than default (and want to handle encryption), they would using a custom class.



--
This message was sent by Atlassian JIRA
(v6.2#6252)