Ensure PROJECT_CREATION_UPLOAD same behaviour for tagging when autocr… #5140
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.
Description
This PR fixes an authorization inconsistency regarding tag handling for users with the
PROJECT_CREATION_UPLOAD
permission during project auto-creation/update forPUT/POST
/v1/bom
resourceUsers with only the
PROJECT_CREATION_UPLOAD
permission were previously able to:Update tags when bom upload, even without
PORTFOLIO_MANAGEMENT
permission and could not do the same for existing projects.This led to inconsistent permission boundaries
Tag creation or updates are now entirely blocked for users who only have the
PROJECT_CREATION_UPLOAD
permission - regardless of whether the project is being created or updated.Proper tag handling (both creation and modification) now consistently requires the
PORTFOLIO_MANAGEMENT
permission.Addressed Issue
#5127
Checklist