[fix] check user extension access #2519
Merged
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
It was previously possible for a user to access an installed extension even if the user did not explicitly enabled that extension.
With this PR the
enable/disablestate for an extension is enforced for both the UI and the API.Prerequisite for #2516
Test Scenario
gertyfor example)Not foundgertyas admin (but do not enable)User extension 'gerty' not enabled.gertygertyUser extension 'gerty' not enabled.gertygertygertygerty