[ https://issues.apache.org/jira/browse/NIFI-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480181#comment-16480181 ]
ASF GitHub Bot commented on NIFI-4199: -------------------------------------- Github user jvwing commented on a diff in the pull request: https://github.com/apache/nifi/pull/2704#discussion_r189164994 --- Diff: nifi-nar-bundles/nifi-aws-bundle/nifi-aws-abstract-processors/src/main/java/org/apache/nifi/processors/aws/AbstractAWSProcessor.java --- @@ -92,6 +94,23 @@ .addValidator(StandardValidators.PORT_VALIDATOR) .build(); + public static final PropertyDescriptor PROXY_USERNAME = new PropertyDescriptor.Builder() + .name("Proxy Username") + .description("Proxy username") + .expressionLanguageSupported(true) + .required(false) + .addValidator(StandardValidators.NON_EMPTY_VALIDATOR) + .build(); + + public static final PropertyDescriptor PROXY_PASSWORD = new PropertyDescriptor.Builder() + .name("Proxy Password") --- End diff -- I recommend a separate `name` vs `displayName` for PROXY_PASSWORD. > NiFi processors should be able to share proxy settings > ------------------------------------------------------ > > Key: NIFI-4199 > URL: https://issues.apache.org/jira/browse/NIFI-4199 > Project: Apache NiFi > Issue Type: Improvement > Reporter: Andre F de Miranda > Assignee: Koji Kawamura > Priority: Major > > Currently, configuring proxy settings for NiFi processors may be a tedious > process that requires the DFM to set proxy settings on individual processors. > This leads to: > * Duplication of work > * Management overhead (as password must be changed on multiple locations) > * Lower security (as proxy credentials must be known by "n" DFMs) > Ideally, NiFi should offer a way to minimise duplication of work by offering > a something similar to the Standard SSL Context services. This way, the DFM > could set the proxy settings once an all authorised users could tap into > those settings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)