[jira] [Updated] (NIFI-7593) Azure Blob Storage uses sensitive property for account name

2021-04-28 Thread Joey Frazee (Jira)


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

Joey Frazee updated NIFI-7593:
--
Labels: easyfix  (was: easyfix newbie)

> 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)


[jira] [Updated] (NIFI-7593) Azure Blob Storage uses sensitive property for account name

2021-04-28 Thread Joey Frazee (Jira)


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

Joey Frazee updated NIFI-7593:
--
Labels: easyfix newbie  (was: easyfix)

> 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, newbie
>
> 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)