Siddharth Wagle created AMBARI-6344:
---------------------------------------
Summary: 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)