Motivation
You may have an unruly registered users (e.g. a crawler program) who don't follow the rules.
You may not have control over such a crawler. And the web application container in which TWiki is installed may be managed by somebody else and you don't have tight and quick control.
Description and Documentation
Introduce $TWiki::cfg{ForbidUserAction} having a hash reference. The key of the hash is the internal user name and the value is a comma separated list of script names such as view and edit. The specificied scripts are forbidden for the user with all topics of all webs.
If the list is preceded by !, only the listed scripts are permitted and the other scripts are forbidden for the user.
Examples
$TWiki::cfg{ForbidUserAction} = {
AggressiveCrawler => 'edit, oops, search',
TotallyForbidden => '!nothing',
};
Impact
Implementation
--
Contributors:
Hideyo Imazu - 2014-10-16
Discussion
Special case, I am OK with this. Could that be done with an Apache Deny rule? Or a configuration on the greedy crawler?
--
Peter Thoeny - 2014-10-16
It can be accomplished by Apache configuration. But the web application container may be managed by a different team from the team owning a web application. In that case forbidding users at the TWiki level is handy.
--
Hideyo Imazu - 2014-10-16
Accepted by release meeting at
KampalaReleaseMeeting2014x10x16.
--
Peter Thoeny - 2014-10-17