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

ASF GitHub Bot commented on NIFI-5625:
--------------------------------------

Github user alopresto commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/3020#discussion_r219712821
  
    --- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/GetHTTP.java
 ---
    @@ -177,19 +180,22 @@
                 .name("Username")
                 .description("Username required to access the URL")
                 .required(false)
    +            
.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
                 .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
                 .build();
         public static final PropertyDescriptor PASSWORD = new 
PropertyDescriptor.Builder()
                 .name("Password")
                 .description("Password required to access the URL")
                 .required(false)
                 .sensitive(true)
    +            
.expressionLanguageSupported(ExpressionLanguageScope.VARIABLE_REGISTRY)
    --- End diff --
    
    Our policy so far has been that passwords do not support expression 
language, for a couple reasons:
    1. How to evaluate if a password `abc${def}` should be interpreted as `abc` 
+ *the value of(`def`)* or the literal string `abc${def}`
    1. The variable registry is not designed to store sensitive values 
securely, so if a password is stored here, it can be accessed by an 
unauthorized user


> Support variables  for the properties of HTTP processors
> --------------------------------------------------------
>
>                 Key: NIFI-5625
>                 URL: https://issues.apache.org/jira/browse/NIFI-5625
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions, Variable Registry
>    Affects Versions: 1.7.1
>            Reporter: Kemix Koo
>            Priority: Minor
>
> When set some group (global) variables, some properties of HTTP processors 
> don't support the expressions. for example, USER and PASS, if don't set the 
> global variables, must change for each processors one by one. it's so 
> troublesomely. 



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

Reply via email to