Checking module permissions before the module launch #4123
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.
This PR adds functionality that checks whether module is permitted to launch for the user.
The approach is the following:
Modulecapability, viamodules_setupinner script, a configuration file (SitePackage.lua) and auxiliary shell script (CheckPermissions.sh) are being created in theCP_CAP_MODULES_CONFIG_DIRpermissions.jsonin the module directory then:modein the file is restriction by usernames - then checks whether current user is in the permitted list (inpermissions.json)modein the file is restriction by locations - then checks whether location of the current user is in the permitted list (inpermissions.json)permissions.jsonin the module directory then module is launched without any additional validationsAdditional details:
CheckPermissions.shshell script that is being launched from module configuration file (SitePackage.lua) and located in the same directory (CP_CAP_MODULES_CONFIG_DIR)$API_TOKEN)user_region)