You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2022/11/10 16:45:00 UTC

[jira] [Resolved] (NIFI-7486) Make InvokeHttp authentication properties able to read from variables.

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

David Handermann resolved NIFI-7486.
------------------------------------
    Resolution: Won't Fix

Parameters and Parameter Context are the recommended way for providing environment-specific credentials. The introduction of Parameter Providers in NiFi 1.18.0 enables Parameters to be sourced from environment variables, so this is the recommend approach instead of Variables, which will likely be phased out in future major releases.

> Make InvokeHttp authentication properties able to read from variables.
> ----------------------------------------------------------------------
>
>                 Key: NIFI-7486
>                 URL: https://issues.apache.org/jira/browse/NIFI-7486
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.11.4
>            Reporter: Alexandre Moraes do Nasciment
>            Priority: Minor
>              Labels: InvokeHTTP, custom_processor, extension
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> The Basic Authentication Username and Basic Authentication Password cannot be read from variables and environment variables. So if the credentials change, it should be fixed in each processor. Adding support to expression language scope variable registry may solve the problem.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)