[
https://issues.apache.org/jira/browse/NIFI-10473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608863#comment-17608863
]
ASF subversion and git services commented on NIFI-10473:
--------------------------------------------------------
Commit ece83709f4769fe4b0950c1aa4b32a559599385f in nifi's branch
refs/heads/main from Joe Gresock
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ece83709f4 ]
NIFI-10473: Removing referencing components check on param provider f… (#6388)
* NIFI-10473: Removing referencing components check on param provider fetch
* NIFI-10473: Adding parameter status DTO to ParameterProviderDTO
* Allowing parameterStatus to be populated even when no parameters were updated
* Adding ParameterStatus enum for parameter fetching
* Adding MISSING_BUT_REFERENCED ParameterStatus
This closes #6388
> Parameter Provider Fetch REST call authorization check is too restrictive
> -------------------------------------------------------------------------
>
> Key: NIFI-10473
> URL: https://issues.apache.org/jira/browse/NIFI-10473
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Joe Gresock
> Assignee: Joe Gresock
> Priority: Minor
> Fix For: 1.18.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When bringing up the Fetch Parameters dialog, if the user is not authorized
> on any referencing component, the dialog fails to load. This is overly
> restrictive, as NiFi already prevents applying the parameters in this
> scenario.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
