[
https://issues.apache.org/jira/browse/NIFI-14955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18019359#comment-18019359
]
Pierre Villard commented on NIFI-14955:
---------------------------------------
Yeah I'd classify it as a feature request for the UI team (may also need some
backend changes, not sure). I believe this is something that [~mcgilman]
investigated at some point but not sure what is the latest on this.
> Identify correctly whether a sensitive field references a value or a parameter
> ------------------------------------------------------------------------------
>
> Key: NIFI-14955
> URL: https://issues.apache.org/jira/browse/NIFI-14955
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 2.0.0
> Environment: All
> Reporter: Craig Patrick
> Priority: Major
> Attachments: image-2025-09-10-14-58-12-072.png,
> image-2025-09-10-14-59-49-539.png, image-2025-09-10-15-00-11-090.png,
> image-2025-09-10-15-01-03-738.png
>
>
> I'm not sure if this is a bug or a feature request based on how the current
> functionality works so I'll explain the situation and let you decide - based
> on current behaviour I think this may be a bug.
> When a field requires a sensitive value, there is currently no way to
> identify whether the field contains an actual value, or a reference to a
> parameter (the caveat to this being when you first enter a parameter
> reference, and then it does show)
> Example:
> InvokeHTTP with a sensitive value for Authorization header... when we click
> to edit this, it shows "Convert to Parameter" even though this *IS* a
> parameter reference:
> !image-2025-09-10-14-58-12-072.png!
> If I edit the field, and add the reference to a parameter once again, then
> instead if we try and change this value a second time (before applying the
> change), we get the "Go To Parameter" option instead (which indicates it's a
> parameter not a value):
> !image-2025-09-10-14-59-49-539.png!
> !image-2025-09-10-15-00-11-090.png!
> However - as soon as we apply the change, and edit the parameter once more it
> reverts back to the "Convert to Param" menu option:
> !image-2025-09-10-15-01-03-738.png!
>
> I guess this ticket is to either:
> _Correct the current functionality so that if a parameter is entered as a
> value for a sensitive field, that the "Go To Parameter" option correctly
> shows every time you click on the context menu_
> *- or -*
> _Add new functionality to the UI so you can clearly see if a sensitive field
> contains a value or a parameter reference_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
