Repository navigation
Fix Extension Management permission validation - #12390
PooyaKharamesh wants to merge 4 commits into
Conversation
Backport the corrected permission-set checks and regression tests, including the namespace and test compilation repairs from Bug 651703. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
This backport targets |
Good Sense Reviewer - Round 1Recommendation: Reject ChangesWhat this PR doesThis change replaces a broad metadata read-permission proxy with explicit tenant-wide checks for The production permission logic is focused and matches the tenant-wide authorization boundary. However, the new test subscriber is not valid in a test codeunit, so the changed test app cannot compile. Problem-solution fitFit: Strong The change directly addresses the missing authorization boundary and covers the main allowed and denied assignments. The implementation is not merge-ready because the added test authorization subscriber prevents the test app from compiling. SuggestionsS1 (🔴 High): Static subscriber prevents the test app compiling Risk assessment and necessityRisk: Extension installation, removal, and orphan-data deletion are tenant-wide administrative operations. The explicit permission checks are narrow and match the established implementation, but the regression tests cannot compile or run in their current form. Necessity: Replacing the table-read proxy is needed because it does not prove extension-management authority. This backport targets an unsupported release branch, so it should be closed or moved to a supported branch after the test subscriber is corrected.
|
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Good Sense Reviewer - Round 2Recommendation: Reject ChangesWhat this PR doesThis change replaces the broad application-object read-permission check with explicit tenant-wide The round-1 compilation blocker is resolved. The strict application build passes, while the default jobs fail before compilation because a baseline artifact is unavailable. However, this backport targets Status of previous suggestions
New observations (commits since round 1)None - the changes address the previous suggestion and reorder declarations only. Risk assessment and necessityRisk: The authorization check protects tenant-wide extension installation, removal, and related data-deletion operations. The round-2 commits only repair the test harness and preserve the explicit-user permission tests. The strict build passes; the default failures occur before compilation and do not provide a code diagnostic. Necessity: Explicit permission validation is needed because application-object read access is not extension-management authority. This PR should not merge through
|
|
Closing this PR because its target branch is unsupported and will not be merged here. The authorization-hardening change and any remaining review/build follow-up will be fixed in separate PRs targeting supported branches. |
1 similar comment
|
Closing this PR because its target branch is unsupported and will not be merged here. The authorization-hardening change and any remaining review/build follow-up will be fixed in separate PRs targeting supported branches. |
Pull request was closed
Fixes missing permission validation in Extension Management.
Related to AB#648158