[
https://issues.apache.org/jira/browse/NIFI-7550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-7550.
------------------------------------
Resolution: Incomplete
This issue as written incorporates a number of possible improvements to
Sensitive Parameters, but does not include specific updates planned. Supporting
dynamic sensitive properties will address some of the issues raised in the
description. More general improvements could be described in a new feature
proposal, or specific improvements can be addressed in focused issues.
> Improve population and use of sensitive parameters
> --------------------------------------------------
>
> Key: NIFI-7550
> URL: https://issues.apache.org/jira/browse/NIFI-7550
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration Management, Core Framework
> Affects Versions: 1.11.4
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Major
> Labels: configuration, credentials, expression-language,
> parameter, properties, sensitive, variable
>
> There has been a lot of discussion recently around the challenges in
> deploying sensitive values (credentials, tokens, etc.) to specific processor
> properties.
>
> * Expression Language does not support sensitive variables
> * Sensitive properties do not support Expression Language
> * Sensitive properties can only reference sensitive parameters
> * Sensitive properties can only reference a single sensitive parameter
> * Sensitive parameters cannot be operated on by Expression Language
> * Sensitive properties which require constructed input (i.e.
> {{Authorization: bearer ABCDEF...}} header) require the sensitive parameter
> to contain format information separate from the sensitive value
> * Sensitive parameters cannot be automatically populated by an external
> source
> Please comment on this ticket with any additional requirements or challenging
> user experiences to inform the next set of decision-making around the
> sensitive parameter experience.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
