[jira] [Commented] (NIFI-5546) PutAzureBlobStorage not able to configure

["Sivaprasanna Sethuraman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16592892#comment-16592892 ] 

Sivaprasanna Sethuraman commented on NIFI-5546:
-----------------------------------------------

[~rakeshsilswal]

This is actually not a bug. Azure Storage account can be accessed by two ways:
 # Storage account name & storage account key - This key is the master key. A person who has this combination can do any operations on this storage account
 # SAS Token - This provides more granular access control. You can create SAS token to only read from a storage account.

When you are working SAS, you don't need a storage account key and vice versa, but in both cases you would need the Storage account name and that is why the properties are defined and validated like that.

> PutAzureBlobStorage not able to configure
> -----------------------------------------
>
>                 Key: NIFI-5546
>                 URL: https://issues.apache.org/jira/browse/NIFI-5546
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 1.6.0, 1.7.0
>            Reporter: Rakesh Prasad
>            Priority: Major
>
> to configure PutAzureBlobStorage processor we have 2 properties that are marked as not null.
> ACCOUNT_KEY = NON_EMPTY_VALIDATOR
> PROP_SAS_TOKEN = NON_EMPTY_VALIDATOR
> but inside "AzureStorageUtils" class we have additional code that is asking for either one on the value, but not both.
> String sasToken = validationContext.getProperty(PROP_SAS_TOKEN).getValue();
>  String acctName = validationContext.getProperty(ACCOUNT_KEY).getValue();
>  if ((StringUtils.isBlank(sasToken) && StringUtils.isBlank(acctName))
>  || (StringUtils.isNotBlank(sasToken) && StringUtils.isNotBlank(acctName))) {
>  results.add(new ValidationResult.Builder().subject("AzureStorageUtils Credentials")
>  .valid(false)
>  .explanation("either Azure Account Key or Shared Access Signature required, but not both")
>  .build());
>  }
>  
> because of this, not able to use this processor.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)