[jira] [Resolved] (AMBARI-22259) Include property key type under consideration for smartsense anonymization

["Juanjo Marron (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-22259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juanjo Marron resolved AMBARI-22259.
------------------------------------
    Resolution: Feedback Received

After conversation with SmartSense Dev team it will be considered in next releases.
For now there are anonymization rules available based on specific property name, so this case is cover.

> 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
>            Priority: Major
>
> 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)