[ https://issues.apache.org/jira/browse/NIFI-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joey Frazee resolved NIFI-7593. ------------------------------- Resolution: Not A Problem [~malthe] This is intentional as account names can correspond to publicly accessible resources and storing this in plain text or visible to a variety of users presents a security risk if the flow.xml.gz is compromised or a template is unintentionally shared, etc. I agree that it's very unintuitive but it's important to do. I'm going to close this, but I want to ask, do you think it'd be helpful to have this rationale documented somewhere in the user guide? > Azure Blob Storage uses sensitive property for account name > ----------------------------------------------------------- > > Key: NIFI-7593 > URL: https://issues.apache.org/jira/browse/NIFI-7593 > Project: Apache NiFi > Issue Type: Improvement > Reporter: Malthe Borch > Priority: Minor > Labels: easyfix > > Processors such as > [AzureListBlobStorage|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-azure-nar/1.5.0/org.apache.nifi.processors.azure.storage.ListAzureBlobStorage/] > has account name as a sensitive property. > This seems wrong and also causes some usability issues with parameter context > parameters (which are either sensitive or non-sensitive). > Note that while the fix for this is trivial, it could have real implications > for existing flows. -- This message was sent by Atlassian Jira (v8.3.4#803005)