Summary: | Many plugins require the full plugins permission set to run | ||
---|---|---|---|
Product: | Koha | Reporter: | Martin Renvoize (ashimema) <martin.renvoize> |
Component: | Plugin architecture | Assignee: | Martin Renvoize (ashimema) <martin.renvoize> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | 1joynelson, alban.peyrat_koha, fridolin.somers, jonathan.druart, kyle, lucas, m.de.rooy, martin.renvoize, nick |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36205 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Martin Renvoize (ashimema)
2021-09-07 08:53:34 UTC
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, |