01.12.2012 Views

7 Components: the Function Pages - Developers

7 Components: the Function Pages - Developers

7 Components: the Function Pages - Developers

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

···*·Set NOSEARCHALL = on<br />

O<strong>the</strong>rwise, <strong>the</strong> web will be included in a full-text search. With regard<br />

to viewing restrictions, remember that a search requires registration<br />

as soon as blocked content is to be displayed. If a visitor does<br />

not have a user name, he or she cannot use <strong>the</strong> search in this case.<br />

The same applies to viewing topics and editing.<br />

If you decide to protect a web from unauthorized access, you<br />

should also define <strong>the</strong> permissions of <strong>the</strong> preferences page. This is<br />

done, as usual, with <strong>the</strong> parameter ALLOWTOPICCHANGE, since it<br />

pertains to a single page.<br />

This also means that a priority list must be generated for <strong>the</strong> event<br />

that topic and web settings are different. Normally, topic settings<br />

have priority. Thus, as you can see, decisions regarding access to individual<br />

topics are in <strong>the</strong> hands of <strong>the</strong> respective authors.<br />

The only setting that pertains to <strong>the</strong> entire TWiki is <strong>the</strong> permission<br />

to generate new webs. It is defined via TWikiPreferences. If you<br />

prefer not to have access limits in your TWiki, you should remove<br />

<strong>the</strong> following entries:<br />

···*·Set ALLOWWEBMANAGE = User, Groups<br />

···*·Set DENYWEBMANAGE = User, Groups<br />

since you o<strong>the</strong>rwise will not be able to add new webs.<br />

Now, <strong>the</strong>re is still one serious security problem: An inexperienced<br />

user who tries to change settings changes <strong>the</strong><br />

ALLOWTOPICCHANGE for a topic. In doing so, he makes a typing<br />

mistake or, if acting malevolently, knowingly enters a non-existent<br />

user. From <strong>the</strong>n on, nobody can edit <strong>the</strong> page! One would have to lift<br />

<strong>the</strong> password protection temporarily in order to manually fix <strong>the</strong><br />

problem. However, this would lead to considerable problems for users<br />

logged in at <strong>the</strong> time, because <strong>the</strong>ir permission verification only<br />

works through au<strong>the</strong>nticated pages. To avoid such problems, a SuperAdmin<br />

Group can be set up that always has edit permissions for<br />

all topics. This group is activated by default and can be set up at<br />

TWikiAdminGroup. If you do not want such a group, or would like<br />

to grant ano<strong>the</strong>r group <strong>the</strong>se rights, you need to change <strong>the</strong> file<br />

Twiki.cfg in <strong>the</strong> directory lib. The two relevant parameters are<br />

$superAdminGroup = "TWikiAdminGroup"<br />

$doSuperAdminGroup = "1"<br />

Priorities in<br />

issuing<br />

permissions<br />

Wiki-wide<br />

permissions<br />

SuperAdmin<br />

Group<br />

14.4 Access Control �<br />

�<br />

�<br />

211

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!