NIFI-15845 Remove Restricted Component Authorization from Framework - #11148
Merged
Conversation
pvillard31
approved these changes
Apr 16, 2026
pvillard31
left a comment
Contributor
There was a problem hiding this comment.
LGTM, thanks @exceptionfactory
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
NIFI-15845 Removes component authorization handling from the framework for the
Restrictedannotation and associated Required Permissions.This removal follows approval of NIP-24 deprecating the
Restrictedannotation, which was released in Apache NiFi API 2.8.0, and was incorporated in the release of Apache NiFi 2.9.0.The removal does not require any changes to existing installations on subsequent upgrades.
The changes remove checking for the
Restrictedannotation on extension component classes and remove computation of required permissions from those classes. All other authorization checks remain, meaning that components with theRestrictedannotation now fall under the same authorization requirements as any other component class.This initial set of changes is scoped to framework classes responsible for verifying restricted authorization, without involving any changes to REST API payloads, frontend features, or component classes. Changes to these other areas can be addressed independently after making these framework changes.
Key changes include the following:
FileAccessPolicyProviderandResourceTypeComponentAuthorizableand implementations/restricted-componentspolicies inStandardAuthorizableLookupfor legacy policy definitionsTracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking
Pull Request Tracking
NIFI-00000NIFI-00000VerifiedstatusPull Request Formatting
mainbranchVerification
Please indicate the verification steps performed prior to pull request creation.
Build
./mvnw clean install -P contrib-checkLicensing
LICENSEandNOTICEfilesDocumentation