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/08/17 18:22:00 UTC

[jira] [Resolved] (NIFI-6995) InvokeHTTP processor Auth user name didn't support registry variable

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

David Handermann resolved NIFI-6995.
------------------------------------
    Resolution: Workaround

As mentioned in comments, integrating Parameter Contexts provides the recommend solution for reusable component configurations.

> InvokeHTTP processor Auth user name didn't support registry variable
> --------------------------------------------------------------------
>
>                 Key: NIFI-6995
>                 URL: https://issues.apache.org/jira/browse/NIFI-6995
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.9.2
>            Reporter: tony wang
>            Priority: Minor
>
> InvokeHTTP processor property (Basic Authentication Username) didn't support registry variable and any changes to this value will impact the nifi registry version management.  It's hard to managed it cross multiple environment in case different user id used.
> It will be better ether mark this property as secure or support registry variable



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