You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Akshay Kotecha Jain (JIRA)" <ji...@apache.org> on 2017/10/17 22:29:01 UTC
[jira] [Created] (AMBARI-22259) Include property key type under
consideration for smartsense anonymization
Akshay Kotecha Jain created AMBARI-22259:
--------------------------------------------
Summary: Include property key type under consideration for smartsense anonymization
Key: AMBARI-22259
URL: https://issues.apache.org/jira/browse/AMBARI-22259
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Reporter: Akshay Kotecha Jain
Currently, smart-sense anonymization uses a service's property name to detect any passwords or sensitive data to replace it with a random hashed value. However, this does not work if the type of the property is set to *_PASSWORD_* but the name of the property does not match the expression found in the following anonymization rule snippet:
{color:red} {
"name": "PASSWORDS",
"rule_id": "Property",
"properties": [".*password.*", ".*awsAccessKeyId.*", ".*awsSecretAccessKey.*", ".*awsAccessKeyId.*", "fs.azure.account.key.*", "ranger.service.https.attrib.keystore.pass"],
"include_files": ["*.xml", "*.properties", "*.yaml", "*.ini"],
"exclude_files" : ["capacity-scheduler.xml"],
"shared": false
}{color}
Smart-sense should consider both the name and the type of the property to apply anonymization.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)