[
https://issues.apache.org/jira/browse/NIFI-14955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020893#comment-18020893
]
Craig Patrick commented on NIFI-14955:
--------------------------------------
Thanks [~mcgilman] - I think as long as something in the UI reflects that the
sensitive value is a parameter in it's entirety as you suggest, then that would
be very beneficial. At the moment, you can't even see WHAT the parameter name
is if it's set and so trying to establish what the value is or change it is a
real mystery.
If this is worked on by a developer who then leaves the organisation, it would
be nigh on impossible for a following developer to be able to check this
integration and see which parameter is being referenced here. Would require
them to basically add the correct parameter reference regardless of whether
this is the current one or not.
I also don't see any issues in using the "Go To Parameter" options for
sensitive values referencing a parameter, as the resulting parameter is
obfuscated anyway so no one would be able to see the actual value, only that
this is the current referenced parameter, but that's just my opinion.
> 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)
