Some plugins with hooks into the UI outside of the tools and plugin management page require the overall 'plugins' permission to run. This however has the side effect of allowing users with those permissions to also manage plugins which may not be the effect wanted. Example: A site has both an Online Payments plugin and the CLA Permissions Check plugin installed. To use the button from the catalogueing toolbar for the CLA plugin you are required to have the overall plugins permission. This then exposes the login credentials for the Online payments plugin as the user gets access to the tools pages.
Do we need to fix the permissions in Koha or in the plugins?
In the case of the CLA plugin, we add a button that triggers a call to `plugins/run.pl?class=[% CLASS %]&method=...` Anything that follows that pattern to trigger a plugin method to run, will require some more involved permissions. In the CLA case, I think I'd like to generally modernise the approach so we don't need to call the run method.. so I'm not sure what wider effects this may have on other plugins.
I run into the same problem. Indeed the permissions are on the plugin method : https://git.koha-community.org/Koha-community/Koha/src/commit/ac02c1d2adc883cc6ff6b749c271cb165d337436/plugins/run.pl#L40 But currently only exists tool and report and plugins create there own methods. Should we change for only one subpermission "run plugin" ? And plugins have to implement permissions. Best regards,