[
https://issues.apache.org/jira/browse/NIFI-15952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Patrick resolved NIFI-15952.
----------------------------------
Resolution: Not A Problem
Apologies, this was based on duplicated contexts for some reason, which has now
been resolved
> Changing parameter values for a referenced SSL context ID does not update
> -------------------------------------------------------------------------
>
> Key: NIFI-15952
> URL: https://issues.apache.org/jira/browse/NIFI-15952
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.7.0
> Reporter: Craig Patrick
> Priority: Major
> Attachments: image-2026-05-19-09-35-09-032.png,
> image-2026-05-19-09-36-07-582.png, image-2026-05-19-09-37-07-622.png
>
>
> When using a reference parameter for an SSL Context within an invokeHTTP
> processor, updating the parameter value is not taking effect in the processor.
> Example:
> * Create InvokeHTTP processor using a reference parameter for the SSL
> Context ID
> * Save to Registry and deploy to different environment
> * Invoke correctly reports that service with ID ABC123 can not be found
> * Update parameter to the new ID of the context service "XYZ456"
> * Parameter change does not take effect when trying to save the processor
> and it fails to start...
> Images:
> !image-2026-05-19-09-35-09-032.png!
> Context Params:
> !image-2026-05-19-09-36-07-582.png!
> Error:
> !image-2026-05-19-09-37-07-622.png!
> It's as if updating and saving the parameter is not taking effect, maybe a
> cache or something not bubbling up?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
